[Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
The photos in comments #12 and #13 show the Ubuntu Yaru theme is not being used (missing the logo aside from this cursor bug), so it makes some sense if whatever theme that is requires more of Adwaita than regular Ubuntu does. ** Summary changed: - [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) + GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) ** Package changed: ubuntu => gdm3 (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (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/1972080 Title: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
Maybe start by removing the package 'sabily-gdm-themes' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello again Zhanglei. This means that so far: 3000: BUG 3002: NO BUG 3003: NO BUG 3004: NO BUG You can find kernel 3005 here: https://kernel.ubuntu.com/~kmously/kernel-kmously-039f206-aRqC/ Please ensure you are running version -3005. 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/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973258] [NEW] downloads won't work in any directory apart from the default one using any browser.
Public bug reported: Downloads won't work when I change the directory while trying to download something. Whatever, the directory opens up by default in the nautilus window when downloading, it would save the file only at that particular location. If I try to save at any other location, the nautilus window would just close normally but the download won't start. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 13 10:22:31 2022 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-04-13 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1973258 Title: downloads won't work in any directory apart from the default one using any browser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1973258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Thanks Zhanglei. I am building 3005 now. It should be ready in about 30 minutes. I will update again soon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Sorry. Like this?
for (tc = 0U; tc < self->aq_nic_cfg.tcs; tc++) {
for (i = 0U; self->aq_vecs > i; ++i) {
aq_vec = self->aq_vec[i];
if (!aq_vec)
break;
data += count;
count = aq_vec_get_sw_stats(aq_vec, tc, data);
}
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958770
Title:
Aquantia GbE LAN driver causes UBSAN error during kernel boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973257] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.3 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error
Public bug reported:
System info:
Description:Ubuntu 20.04.4 LTS
Release:20.04
Linux kot9ra-Air 5.17.7+ #2 SMP Fri May 13 05:27:24 BST 2022 x86_64 x86_64
x86_64 GNU/Linux
Building log:
Building for 5.17.7+
Building for architecture x86_64
Building initial module for 5.17.7+
ERROR (dkms apport): kernel package linux-headers-5.17.7+ is not supported
Error! Bad return status for module build on kernel: 5.17.7+ (x86_64)
Make.log:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.17.7+ (x86_64)
Fri 13 May 05:44:12 BST 2022
make: Entering directory '/usr/src/linux-headers-5.17.7+'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:794:3:
note: in expansion of macro ‘WL_DBG’
794 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:795:2:
note: here
795 | default:
| ^~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:81:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.h:73: warning:
"isprint" redefined
73 | #define isprint(c) bcm_isprint(c)
|
In file included from ./include/linux/string_helpers.h:6,
from ./include/linux/seq_file.h:7,
from ./include/linux/seq_file_net.h:5,
from ./include/net/net_namespace.h:183,
from ./include/linux/netdevice.h:37,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:69,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:27:
./include/linux/ctype.h:30: note: this is the location of the previous
definition
30 | #define isprint(c) ((__ismask(c)&(_P|_U|_L|_D|_SP)) != 0)
|
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/osl.h:79,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:28:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function
‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:645:36:
warning: passing argument 1 of ‘memcpy’ discards ‘const’ qualifier from pointer
target type [-Wdiscarded-qualifiers]
645 | bcopy(>pub->cur_etheraddr, dev->dev_addr, ETHER_ADDR_LEN);
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linux_osl.h:156:39:
note: in definition of macro ‘bcopy’
156 | #define bcopy(src, dst, len) memcpy((dst), (src), (len))
| ^~~
In file included from ./include/linux/string.h:253,
from ./include/linux/bitmap.h:11,
from ./include/linux/cpumask.h:12,
from ./arch/x86/include/asm/cpumask.h:5,
from ./arch/x86/include/asm/msr.h:11,
from ./arch/x86/include/asm/processor.h:22,
from ./arch/x86/include/asm/timex.h:5,
from ./include/linux/timex.h:65,
from ./include/linux/time32.h:13,
from ./include/linux/time.h:60,
from ./include/linux/stat.h:19,
from ./include/linux/module.h:13,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:40,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:27:
./include/linux/fortify-string.h:212:37: note: expected ‘void *’ but argument
is of type ‘const unsigned char *’
212 | __FORTIFY_INLINE void *memcpy(void *p, const void *q, __kernel_size_t
size)
| ~~^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function
‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:784:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
784 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:786:3: note:
...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
786 | bar1_size = pci_resource_len(pdev, 2);
| ^
In file included from
[Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
The following two lines shouldn't be omitted: data += count; count = aq_vec_get_sw_stats(aq_vec, tc, data); -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Kahled, Version 3004 hot plug can pass. thanks //Mao -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 642978] Re: gpicview "save as" dialogue confusing
[Expired for gpicview (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gpicview (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/642978 Title: gpicview "save as" dialogue confusing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpicview/+bug/642978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973254] Re: uc22 pc-kernel 5.15.0-30.31.1 iwlwifi Hardware error detected. Restarting.
Attaching dmesg-boot.txt ** Attachment added: "dmesg-boot.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1973254/+attachment/5589369/+files/dmesg-boot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973254 Title: uc22 pc-kernel 5.15.0-30.31.1 iwlwifi Hardware error detected. Restarting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1973254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973254] [NEW] uc22 pc-kernel 5.15.0-30.31.1 iwlwifi Hardware error detected. Restarting.
Public bug reported: None of our wifi tests seem to be working on one of the amd64 systems we use for testing full disk encryption. The current kernel snap installed is: pc-kernel 5.15.0-30.31.1 99122/betacanonical✓ kernel When looking through the dmesg output, I found a call trace related to iwlwifi which repeats a lot of times. I've attached a section of it as dmesg.txt, as well as dmesg output from right after a fresh boot (dmesg- boot.txt) so you can see the earlier messages, firmware loading, etc. The relevant firmware line from dmesg is: [ 13.667426] iwlwifi :00:14.3: loaded firmware version 66.f1c864e0.0 QuZ-a0-jf-b0-66.ucode op_mode iwlmvm ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1973254/+attachment/5589367/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973254 Title: uc22 pc-kernel 5.15.0-30.31.1 iwlwifi Hardware error detected. Restarting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1973254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
I have implemented your suggestion, so far no issues. I'm going to kick off my backup now and do some more testing later. ** Patch added: "aq_nic.c.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+attachment/5589366/+files/aq_nic.c.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972802] Re: enable config for fixing 5.17 kernel won't load mok
** Tags added: originate-from-1969557 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority 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/1972802 Title: enable config for fixing 5.17 kernel won't load mok To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1972802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892825] Re: update-locale not perform correctly sanity checks
Verified that the new version does not generated bogus lines on bionic: root@lp-1892825-bionic:~# cp /etc/default/locale /tmp/locale root@lp-1892825-bionic:~# update-locale --locale-file /tmp/locale LANG = C.UTF-8 root@lp-1892825-bionic:~# diff -u /etc/default/locale /tmp/locale --- /etc/default/locale 2022-05-09 15:53:23.0 + +++ /tmp/locale 2022-05-13 03:05:13.859996448 + @@ -1 +1 @@ -LANG=C.UTF-8 +#LANG=C.UTF-8 root@lp-1892825-bionic:~# update-locale --locale-file /tmp/locale LANG=en_US.UTF-8 root@lp-1892825-bionic:~# diff -u /etc/default/locale /tmp/locale --- /etc/default/locale 2022-05-09 15:53:23.0 + +++ /tmp/locale 2022-05-13 03:05:36.008238719 + @@ -1 +1 @@ -LANG=C.UTF-8 +LANG=en_US.UTF-8 root@lp-1892825-bionic:~# update-locale --locale-file /tmp/locale LANG= root@lp-1892825-bionic:~# update-locale --locale-file /tmp/locale LANG root@lp-1892825-bionic:~# diff -u /etc/default/locale /tmp/locale --- /etc/default/locale 2022-05-09 15:53:23.0 + +++ /tmp/locale 2022-05-13 03:05:43.680321932 + @@ -1 +1 @@ -LANG=C.UTF-8 +#LANG= root@lp-1892825-bionic:~# cp /etc/default/locale /tmp/locale root@lp-1892825-bionic:~# update-locale --locale-file /tmp/locale LANG root@lp-1892825-bionic:~# diff -u /etc/default/locale /tmp/locale --- /etc/default/locale 2022-05-09 15:53:23.0 + +++ /tmp/locale 2022-05-13 03:05:56.384458949 + @@ -1 +1 @@ -LANG=C.UTF-8 +#LANG=C.UTF-8 root@lp-1892825-bionic:~# dpkg-query -W locales locales 2.27-3ubuntu1.6 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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-kvm/5.15.0.1006.6)
All autopkgtests for the newly accepted linux-meta-kvm (5.15.0.1006.6) for jammy have finished running. The following regressions have been reported in tests triggered by the package: oss4/4.2-build2010-5ubuntu9 (amd64) digimend-dkms/10-4 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu15 (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-kvm [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 1973240] Re: Wireless mouse shows up under `lsusb` list but doesn't control the cursor
Thanks for the bug report. This sounds like a hardware problem, most likely just new batteries are required. Wired mice or wireless with a dongle use the same code paths so clearly that's working for some mice. I don't think there's any software bug here. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973240 Title: Wireless mouse shows up under `lsusb` list but doesn't control the cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1 --- gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium * Merge with Debian. Remaining change: - Lower gnome-control-center dependency to 41 gnome-remote-desktop (42.1.1-2) unstable; urgency=high * Don't automatically enable the systemd user service (LP: #1973028) * Add postinst to remove the automatic enabling of the user service * debian/control: Lower mutter dependency so that these fixes reach Testing sooner gnome-remote-desktop (42.1.1-1) unstable; urgency=medium * New upstream release (LP: #1970662) - Fixes black screen with virtio on qemu (LP: #1971195) * Drop all patches: applied in new release * Depend on libmutter instead of gnome-shell | budgie-desktop - This is a more accurate dependency * Require libmutter 42.1 for Nvidia fixes * Depend on fuse3 (Closes: #998846) (LP: #1970411) -- Jeremy Bicha Thu, 12 May 2022 15:21:47 -0400 ** Changed in: gnome-remote-desktop (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/1970411 Title: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1970411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970662] Re: Update gnome-remote-desktop to 42.1.1
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1 --- gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium * Merge with Debian. Remaining change: - Lower gnome-control-center dependency to 41 gnome-remote-desktop (42.1.1-2) unstable; urgency=high * Don't automatically enable the systemd user service (LP: #1973028) * Add postinst to remove the automatic enabling of the user service * debian/control: Lower mutter dependency so that these fixes reach Testing sooner gnome-remote-desktop (42.1.1-1) unstable; urgency=medium * New upstream release (LP: #1970662) - Fixes black screen with virtio on qemu (LP: #1971195) * Drop all patches: applied in new release * Depend on libmutter instead of gnome-shell | budgie-desktop - This is a more accurate dependency * Require libmutter 42.1 for Nvidia fixes * Depend on fuse3 (Closes: #998846) (LP: #1970411) -- Jeremy Bicha Thu, 12 May 2022 15:21:47 -0400 ** Changed in: gnome-remote-desktop (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/1970662 Title: Update gnome-remote-desktop to 42.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1 --- gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium * Merge with Debian. Remaining change: - Lower gnome-control-center dependency to 41 gnome-remote-desktop (42.1.1-2) unstable; urgency=high * Don't automatically enable the systemd user service (LP: #1973028) * Add postinst to remove the automatic enabling of the user service * debian/control: Lower mutter dependency so that these fixes reach Testing sooner gnome-remote-desktop (42.1.1-1) unstable; urgency=medium * New upstream release (LP: #1970662) - Fixes black screen with virtio on qemu (LP: #1971195) * Drop all patches: applied in new release * Depend on libmutter instead of gnome-shell | budgie-desktop - This is a more accurate dependency * Require libmutter 42.1 for Nvidia fixes * Depend on fuse3 (Closes: #998846) (LP: #1970411) -- Jeremy Bicha Thu, 12 May 2022 15:21:47 -0400 ** Changed in: gnome-remote-desktop (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971195 Title: gnome-remote-desktop leads to a session crash inside qemu with virtio- vga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973028] Re: gnome-remote-desktop user service is always running
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1 --- gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium * Merge with Debian. Remaining change: - Lower gnome-control-center dependency to 41 gnome-remote-desktop (42.1.1-2) unstable; urgency=high * Don't automatically enable the systemd user service (LP: #1973028) * Add postinst to remove the automatic enabling of the user service * debian/control: Lower mutter dependency so that these fixes reach Testing sooner gnome-remote-desktop (42.1.1-1) unstable; urgency=medium * New upstream release (LP: #1970662) - Fixes black screen with virtio on qemu (LP: #1971195) * Drop all patches: applied in new release * Depend on libmutter instead of gnome-shell | budgie-desktop - This is a more accurate dependency * Require libmutter 42.1 for Nvidia fixes * Depend on fuse3 (Closes: #998846) (LP: #1970411) -- Jeremy Bicha Thu, 12 May 2022 15:21:47 -0400 ** Changed in: gnome-remote-desktop (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973028 Title: gnome-remote-desktop user service is always running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1973028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973175] Re: Window dimensions are changed and appears behind the dock
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1961508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1961508 Dock displaying over window after resuming from blank screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973175 Title: Window dimensions are changed and appears behind the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973150] Re: Plymouth splash text and password fields never displayed in QEMU/KVM
** Summary changed: - Fresh encrypted installation, no field is displayed for entering decryption password, but blindly entering the password succeeds + Plymouth splash text and password fields never displayed in QEMU/KVM ** Changed in: plymouth (Ubuntu) Importance: Undecided => High ** Changed in: plymouth (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973150 Title: Plymouth splash text and password fields never displayed in QEMU/KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973157] Re: After an encrypted installation, no splash screen or prompt is displayed asking me to remove the installation disk. Pressing any key (not just Enter) causes the system to reboot.
*** This bug is a duplicate of bug 1973150 *** https://bugs.launchpad.net/bugs/1973150 Thanks for the bug report. It's the same logic in Plymouth as in bug 1973150 so I've now generalized bug 1973150 to cover this. ** This bug has been marked a duplicate of bug 1973150 Plymouth splash text and password fields never displayed in QEMU/KVM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973157 Title: After an encrypted installation, no splash screen or prompt is displayed asking me to remove the installation disk. Pressing any key (not just Enter) causes the system to reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973156] Re: Strange graphical glitch during Ubuntu installation when clicking "Install Now" after inputting disk encryption details
Thanks for the bug report. Screen tearing during mode changes is somewhat normal. Even more normal and even more visible in VMs. If that's the only problem then this may not really be a fixable bug. But I am only guessing. Please provide a video of the issue so we can confirm. ** Package changed: gdm3 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973156 Title: Strange graphical glitch during Ubuntu installation when clicking "Install Now" after inputting disk encryption details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1973156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
Nick, Please look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please also reproduce the bug again and as soon as it happens run: journalctl -b0 > journal.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972812 Title: The operating system does not ask for a password after unlocking the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972984] Re: Cannot paste filename into File Save dialog of Firefox Snap
I would have thought Firefox was using GTK3 still like most non-GNOME apps(?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972984 Title: Cannot paste filename into File Save dialog of Firefox Snap To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1972984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973143] Re: [impish] Wayland session limited to 1024x768
Please try selecting 'Ubuntu on Xorg' on the login screen. Please also upgrade to Ubuntu 22.04 as soon as you can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973143 Title: [impish] Wayland session limited to 1024x768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971202] Re: [nouveau][amdgpu] Freeze
** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - [nouveau][amdgpu] Freeze + [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971202 Title: [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971202] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971202 Title: [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972749] Re: Logging into a second Wayland session/user doesn't work [Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"]
Invalid then I suppose. ** Changed in: mutter (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972749 Title: Logging into a second Wayland session/user doesn't work [Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
This bug is closed. But screen sharing is expected to be broken on Chromium+Wayland due to bug 1897454. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968610] Re: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia
I would mark this as a duplicate of bug 1967488 had you said "black" instead of "transparent". But I guess they could still both be the same issue. ** Tags added: jammy nvidia nvidia-wayland wayland 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/1968610 Title: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968610/+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)
Hi, following up on this - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/comments/9 GRUB PARAM - `i915.enable_dc=0 intel_idle.max_cstate=2` has fixed the flicker for me. $ uname -a Linux home 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" -- 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 1967488] Re: Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver)
** Tags added: nvidia nvidia-wayland ** Tags added: jammy ** Tags added: 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/1967488 Title: Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
I think that's a bit different to the original version, which breaks out
the loop as soon as "aq_vec" evaluates to false.
So, instead of
if (aq_vec) {
...
}
Should be
if (!aq_vec)
break;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958770
Title:
Aquantia GbE LAN driver causes UBSAN error during kernel boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
Please try selecting the Xorg option on the login screen. It will either be called 'Ubuntu on Xorg' or just 'Ubuntu'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1970291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971295] Re: Merge net-snmp from Debian unstable for kinetic
Nothing to merge yet. ** Changed in: net-snmp (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/1971295 Title: Merge net-snmp from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1971295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972829] Re: 22.04 tomcat9 with openjdk8 JSP compilation error
Hey Zoltan thank you very much for the instructions. I also agree that Ubuntu should continue to support Tomcat9 on JDK8 for the same reason. With Debain it is less clear as they do not provided a JDK8 package in the official repositories any more, so I understand their reasoning. As a side note, I would like to say that Debain Bullseye (stable) currently ships with libeclipse-jdt-core-java 4.18 (https://packages.debian.org/bullseye/libeclipse-jdt-core-java), which appears to be compiled for Java 8. I have just successfully installed a Java 8 only tomcat9 web application on Debian Bullseye by installing JRE8 using the third party Adoptium repository to install temurin-8-jdk (see https://adoptium.net/installation/linux) Obviously this does not solve the issue in regards to Ubuntu but I thought the information may be useful to some. It is unfortunate that this workaround will no longer be possible for the next major Debian release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972829 Title: 22.04 tomcat9 with openjdk8 JSP compilation error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/1972829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962166] Re: DEP8 failing with samba 4.15.5
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/backuppc/+git/backuppc/+merge/422252 ** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/backuppc/+git/backuppc/+merge/422253 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962166 Title: DEP8 failing with samba 4.15.5 To manage notifications about this bug go to: https://bugs.launchpad.net/backuppc/+bug/1962166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
** Changed in: linux-gcp (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964527 Title: Enable CONFIG_UNICODE for linux-gcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962225] Re: preinst check that kernel revision < 255 now does more harm than good
Verified that libc6 2.27-3ubuntu1.6 can be installed fine in a bionic docker container an Amazon Linux 2 system with the problematic kernel version: root@eef8e8932f4b:/# apt install libc6 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: glibc-doc locales The following packages will be upgraded: libc6 1 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. Need to get 2831 kB of archives. After this operation, 1024 B disk space will be freed. Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libc6 amd64 2.27-3ubuntu1.6 [2831 kB] Fetched 2831 kB in 1s (3348 kB/s) debconf: delaying package configuration, since apt-utils is not installed (Reading database ... 4140 files and directories currently installed.) Preparing to unpack .../libc6_2.27-3ubuntu1.6_amd64.deb ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debcon f/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype Unpacking libc6:amd64 (2.27-3ubuntu1.6) over (2.27-3ubuntu1.5) ... Setting up libc6:amd64 (2.27-3ubuntu1.6) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debcon f/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype Processing triggers for libc-bin (2.27-3ubuntu1.5) ... root@eef8e8932f4b:/# uname -r 4.14.275-207.503.amzn2.x86_64 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962225 Title: preinst check that kernel revision < 255 now does more harm than good To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973216] Re: No force-feedback for Saitek Cyborg Evo Force
** Package changed: linux (Ubuntu) => joystick (Ubuntu) ** Changed in: joystick (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973216 Title: No force-feedback for Saitek Cyborg Evo Force To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/joystick/+bug/1973216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973237] Re: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade
** Package changed: ubuntu => linux (Ubuntu) ** Package changed: linux (Ubuntu) => unattended-upgrades (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973237 Title: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1973237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
Alas! I spoke to seen. The seeming "workaround" only lasted for one
boot, and after that, the ~180 seconds delay is back to stay, although
the Intel IOMMU is still disabled.
So this issue is "sporadic". Maybe even a race condition... :(
And maybe not even related to the intel-lpss driver: The line:
"intel-lpss :00:15.0: enabling device ( -> 0002)"
seems to come from drivers/pci/setup-res.c:
if (cmd != old_cmd) {
dev_info(>dev, "enabling device (%04x -> %04x)\n",
old_cmd, cmd);
pci_write_config_word(dev, PCI_COMMAND, cmd);
}
So it just enables the PCI device, which at some point leads to
drivers/mfd/intel-lpss.c#intel_lpss_probe() being called which requests
the DMA module leading to drivers/dma/idma64.c#idma64_probe() being
called which finally outputs:
dev_info(chip->dev, "Found Intel integrated DMA 64-bit\n");
So a lot of code between these two log lines:
[6.439056] intel-lpss :00:15.0: enabling device ( -> 0002)
[ 187.141427] idma64 idma64.0: Found Intel integrated DMA 64-bit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welcome screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+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
We will be manually applying 7836. ** Changed in: freerdp2 (Ubuntu Jammy) Status: In Progress => Triaged -- 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
To provide some context, when this crash can happen: It can happen, after attempting to start a remote desktop session, when the screen is locked. In such case, g-s directly refuses the start request and therefore the lifetime of the rdpgfx thread in FreeRDP is very short. The journal message for this looks like this: `Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited` Now, the error here is, that FreeRDP does not correctly wait for the rdpgfx thread to be created and this can lead to in this situation, that the rdpgfx thread is not teared down, when stopping the session, which can can lead to segfaults, like in this report or to memory corruption. Personally, I was not able to reproduce the error. However, with the help of the journal entries I was able to find this cause. https://github.com/FreeRDP/FreeRDP/pull/7836 takes care of the problem. Sessions, that are not locked, should not be affected by this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1970746] Re: New release 101.0.4951.41 for Bionic
Please provide a progress report on testing and validation of this package. Meanwhile, upstream released version 101.0.4951.64 for Linux (version 101.0.4951.67 was only released for Windows). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970746 Title: New release 101.0.4951.41 for Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Thanks Zhanglei. This means that so far: 3000: BUG 3002: NO BUG 3003: NO BUG We are getting closer. This is the remaining set of patches: 00501b41aaf73f (tag: test-3000, tag: fail1) s390/pci: move pseudo-MMIO to prevent MIO overlap 14914e943b0ca5 cpufreq: Fix get_cpu_device() failure in add_cpu_dev_symlink() 02a3dc73620247 rt2x00: do not mark device gone on EPROTO errors during start d0c736f3c95a8e kprobes: Limit max data_size of the kretprobe instances 1101e48029ef8b vrf: Reset IPCB/IP6CB when processing outbound pkts in vrf dev xmit 8ac948debe102a net/smc: Avoid warning of possible recursive locking 844b74044432ab perf report: Fix memory leaks around perf_tip() ef0a82700dd088 perf hist: Fix memory leak of a perf_hpp_fmt 25b5451cf6b834 net: ethernet: dec: tulip: de4x5: fix possible array overflows in type3_infoblock() 79ab9e40571039 net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound 60cbd2bb3e4920 ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() 380cd49e207ba4 ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile 02ce9dcd0056d0 scsi: iscsi: Unblock session then wake up error handler 39fe9db370a672 thermal: core: Reset previous low and high trip during thermal zone init 9c4257be2b4e87 (tag: test-3004) btrfs: check-integrity: fix a warning on write caching disabled disk 7888748df21e65 s390/setup: avoid using memblock_enforce_memory_limit ec02be4afbaa32 platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep ecaf617d2d911f net: return correct error code cf471f304c7bdd atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait ef48e7dac2b4a5 net/smc: Transfer remaining wait queue entries during fallback f5a7ae1664ea55 mac80211: do not access the IV when it was stripped 04e2506c0a0f0e drm/sun4i: fix unmet dependency on RESET_CONTROLLER for PHY_SUN6I_MIPI_DPHY cc02a02a96d745 gfs2: Fix length of holes reported at end-of-file db58cf66b9ed5f can: j1939: j1939_tp_cmd_recv(): check the dst address of TP.CM_BAM 5891df6f755bdc arm64: dts: mcbin: support 2W SFP modules e7ef1451808ba8 of: clk: Make self-contained a8e84f43323809 NFSv42: Fix pagecache invalidation after COPY/CLONE 87243d366e21dd UBUNTU: upstream stable to v5.4.163 8dedcf4867336b Linux 5.4.163 fe61be970fa57f tty: hvc: replace BUG_ON() with negative return value ae65528da134f8 (tag: test-3003, tag: pass2) xen/netfront: don't trust the backend response data blindly The bottom commit (3003) passed and the top commit (3000) failed, so the problem is one of the patches in between. We are now about to test kernel 3004 in the middle. You can find kernel 3004 here: https://kernel.ubuntu.com/~kmously/kernel-kmously-721de44-fWzO/ Please ensure you are running version -3004. 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/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970228] Re: Multiple vulnerabilities in Bionic, Focal and Jammy
** Attachment added: "Upstream tarball for Jammy" https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1970228/+attachment/5589359/+files/subversion-1.14.2.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1970228 Title: Multiple vulnerabilities in Bionic, Focal and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1970228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970228] Re: Multiple vulnerabilities in Bionic, Focal and Jammy
** Patch added: "subversion_jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1970228/+attachment/5589358/+files/subversion_jammy.debdiff ** Changed in: subversion (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1970228 Title: Multiple vulnerabilities in Bionic, Focal and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1970228/+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
Note: 2.7.0 does **NOT** contain https://github.com/FreeRDP/FreeRDP/pull/7836 (which should fix https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970994), because 2.7.0 was released before that MR was created and merged. So you have to either apply https://github.com/FreeRDP/FreeRDP/pull/7836 manually on top of the 2.7.0 build or build from the stable-2.0 branch at a recent commit, depending on what is more convenient for you. -- 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 1967843] Re: cheese display corrupted under Ubuntu 22.04
** Description changed: Impact == The cheese app is unusable with color bands showing in the main view. + This bug doesn't affect all webcams. It's unknown what percentage of + webcams are affected. + Test Case + On a system that experiences this bug: Install the update Run the cheese app Verify that the main view shows what your webcam can see normally. Click the camera button in the bottom toolbar area. Check if the photo looks normal. You can find it in ~/Pictures/Webcam What Could Go Wrong === Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint clutter-gst has been archived by GNOME. (It's recommended for apps to use GTK4 instead of GTK3 + Clutter). That means it's not possible for this patch to be accepted upstream. Instead, distros like Arch Linux are applying this patch. This patch removes 2 renderers that don't work (RGBx and BGRx) but still keeps ones that do work: RGBA and BRGA. Original Bug Report === The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Bug 1973084] Re: transmission-daemon high RAM usage
Sure! I'll do it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973234] Re: Slow Boot, No SOUND, No Ethernet
When the machine is booted, open a terminal and run "dmesg" to see on what the kernel was stuck so long. In my case, it was the intel-lpss PCI device initialization, and I fixed it by disabling the Intel IOMMU. If you get similar results, this issue might be a duplicate of mine which I reported here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973234 Title: Slow Boot, No SOUND, No Ethernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970957] Re: suspend problem
With Wayland, hibernate never works. NVIDIA 510. Switching back to X11, and it works. -- 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 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
After grepping dmesg for all lines about the "00:15" devices, I found two lines starting with "DMAR:", which made me think of another machine running debian which had issues with DMAR: devices that were related to the Intel IOMMU. So I tried the workaround I knew from there: Edit /etc/default/grub and add "intel_iommu=off" to the GRUB_CMDLINE_LINUX_DEFAULT value, then run "sudo update-grub" to update the grub configuration and reboot. and voila, intel-lpss initializes within a few milliseconds again: [6.518592] intel-lpss :00:15.0: enabling device ( -> 0002) [6.560693] idma64 idma64.0: Found Intel integrated DMA 64-bit [6.569509] intel-lpss :00:15.1: enabling device ( -> 0002) [6.569691] idma64 idma64.1: Found Intel integrated DMA 64-bit [6.574164] mei_me :00:16.0: enabling device ( -> 0002) $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID= ro intel_iommu=off So some change between 4.15.0-176 and 4.15.0-177 seemingly broke the Intel IOMMU. Question is whether it was a formerly "dormant" BIOS bug that was only unveiled by some change, or whether it is a newly introduced Linux bug that broke Intel IOMMU support... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973241] Re: Paramiko 2.9.0 breaks compatibility with devices only supporting ssh-rsa and not supporting server-sig-algs
** Changed in: paramiko 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/1973241 Title: Paramiko 2.9.0 breaks compatibility with devices only supporting ssh- rsa and not supporting server-sig-algs To manage notifications about this bug go to: https://bugs.launchpad.net/paramiko/+bug/1973241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973114] Re: Key trust verification fails on Ubuntu 22.04
Validation of package in Kinetic. The validation was run on Jammy with the Kinetic package installed: I have confirmed the bug on a 22.04 image running on AWS: Jammy stock ec2-instance-connect ssh -vvv output: https://pastebin.ubuntu.com/p/jDCnKrGRFM/plain/ When upgrading the package on the same instance with the one from Kinetic (with backported fix), it works: Jammy upgraded (kinetic) ec2-instance-connect ssh -vvv output: https://pastebin.ubuntu.com/p/bkvGwzZDYB/plain/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973114 Title: Key trust verification fails on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970228] Re: Multiple vulnerabilities in Bionic, Focal and Jammy
** Patch added: "subversion_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1970228/+attachment/5589357/+files/subversion_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1970228 Title: Multiple vulnerabilities in Bionic, Focal and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1970228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972043] Re: Please add -ftrivial-auto-var-init=zero to default build flags
Adding it to the compiler means *all* builds benefit, which is the reason this was done on the other options. People build their local projects, newer versions of tools from GitHub, etc etc. This needs to be in the compiler directly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972043 Title: Please add -ftrivial-auto-var-init=zero to default build flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1972043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973133] Re: package linux-image-5.14.0-1036-oem 5.14.0-1036.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (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/1973133 Title: package linux-image-5.14.0-1036-oem 5.14.0-1036.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1973133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920217] Re: id: ‘clamav’: no such user
** Changed in: clamav (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920217 Title: id: ‘clamav’: no such user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969934] Re: Update evolution-data-server to 3.44.1
I have installed the updated packages and restarted. Evolution and GNOME Calendar both still work fine. ** 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/1969934 Title: Update evolution-data-server to 3.44.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
After finding someone reporting the same issue (https://forums.linuxmint.com/viewtopic.php?t=373747=2175201) and reading that the machine may come alive after a while, I found that indeed after 3 minutes the machine works. dmesg that reveals that it seemingly was the initialization of the intel_lpss driver that took 3 minutes: [6.889189] intel-lpss :00:15.0: enabling device ( -> 0002) [7.112397] input: PC Speaker as /devices/platform/pcspkr/input/input5 [7.220480] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer [7.220481] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules [7.220481] RAPL PMU: hw unit of domain package 2^-14 Joules [7.220482] RAPL PMU: hw unit of domain dram 2^-14 Joules [7.220482] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules [7.220483] RAPL PMU: hw unit of domain psys 2^-14 Joules [9.882380] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 10.068162] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 10.070009] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready [ 10.115669] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready [ 10.117735] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 10.61] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 14.114836] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 14.114883] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready [ 15.14] atlantic: link change old 0 new 1000 [ 15.200150] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready [ 187.423062] intel-lpss :00:15.1: enabling device ( -> 0002) [ 187.432242] mei_me :00:16.0: enabling device ( -> 0002) [ 187.432264] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 187.441672] AVX2 version of gcm_enc/dec engaged. [ 187.441673] AES CTR mode by8 optimization enabled [ 187.445619] idma64 idma64.0: Found Intel integrated DMA 64-bit [ 187.452528] idma64 idma64.1: Found Intel integrated DMA 64-bit Note these lines: [6.889189] intel-lpss :00:15.0: enabling device ( -> 0002) [ 187.423062] intel-lpss :00:15.1: enabling device ( -> 0002) [ 187.432242] mei_me :00:16.0: enabling device ( -> 0002) [ 187.445619] idma64 idma64.0: Found Intel integrated DMA 64-bit [ 187.452528] idma64 idma64.1: Found Intel integrated DMA 64-bit For comparison, the same lines from the 4.15.0-176 dmesg: [6.321873] intel-lpss :00:15.0: enabling device ( -> 0002) [6.340549] idma64 idma64.0: Found Intel integrated DMA 64-bit [6.345409] intel-lpss :00:15.1: enabling device ( -> 0002) [6.345610] idma64 idma64.1: Found Intel integrated DMA 64-bit [6.350618] mei_me :00:16.0: enabling device ( -> 0002) So the initialization time increased from 30ms of 180s, i.e. by a factor of 6,000. This cannot be right. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority 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/1967843 Title: cheese display corrupted under Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968957] Re: Cheese displays red-green lines in 22.04
*** This bug is a duplicate of bug 1967843 *** https://bugs.launchpad.net/bugs/1967843 ** This bug has been marked a duplicate of bug 1967843 cheese display corrupted under 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/1968957 Title: Cheese displays red-green lines in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961833] Re: openssh 8.8 breaks login to Canonical servers
interestingly, paramiko is also broken when connecting to older servers, but not for the same reason as this bug. See bug 1973241 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961833 Title: openssh 8.8 breaks login to Canonical servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973241] Re: Paramiko 2.9.0 breaks compatibility with devices only supporting ssh-rsa and not supporting server-sig-algs
Note that for servers showing this problem, using openssh to connect is also broken, but for a different reason (because the ssh-rsa alg is disallowed by default), see bug 1961833 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973241 Title: Paramiko 2.9.0 breaks compatibility with devices only supporting ssh- rsa and not supporting server-sig-algs To manage notifications about this bug go to: https://bugs.launchpad.net/paramiko/+bug/1973241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
** Description changed: - The cheese application produces a corrupted display under Ubuntu 22.04 - with a Logitech C525 webcam. When started from the command line, cheese - produces repeated warnings of the form... + Impact + == + The cheese app is unusable with color bands showing in the main view. + + Test Case + + Install the update + Run the cheese app + Verify that the main view shows what your webcam can see normally. + Click the camera button in the bottom toolbar area. + Check if the photo looks normal. You can find it in ~/Pictures/Webcam + + What Could Go Wrong + === + Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint + + clutter-gst has been archived by GNOME. (It's recommended for apps to + use GTK4 instead of GTK3 + Clutter). That means it's not possible for + this patch to be accepted upstream. Instead, distros like Arch Linux are + applying this patch. + + This patch removes 2 renderers that don't work (RGBx and BGRx) but still + keeps ones that do work: RGBA and BRGA. + + Original Bug Report + === + The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: - SHELL=/bin/bash - LANG=en_US.UTF-8 - TERM=xterm-256color - XDG_RUNTIME_DIR= - PATH=(custom, no user) + SHELL=/bin/bash + LANG=en_US.UTF-8 + TERM=xterm-256color + XDG_RUNTIME_DIR= + PATH=(custom, no user) RelatedPackageVersions: - cheese41.1-1build1 - cheese-common 41.1-1build1 + cheese41.1-1build1 + cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: - cheese41.1-1build1 - cheese-common 41.1-1build1 + cheese41.1-1build1 + cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17
[Bug 1970228] Re: Multiple vulnerabilities in Bionic, Focal, Impish and Jammy
** Description changed: The version in Bionic is vulnerable to CVE-2018-11782, CVE-2019-0203 and CVE-2020-17525. - The version in Focal is vulnerable to CVE-2018-11803 and CVE-2020-17525. + The version in Focal is vulnerable to CVE-2020-17525. - The version in Impish is vulnerable to CVE-2018-11803. - - The version in Jammy is vulnerable to CVE-2018-11803, CVE-2021-28544 and - CVE-2022-24070. + The version in Jammy is vulnerable to CVE-2021-28544 and CVE-2022-24070. Please release patched versions. Debian released a security advisory on April 13. ** Summary changed: - Multiple vulnerabilities in Bionic, Focal, Impish and Jammy + Multiple vulnerabilities in Bionic, Focal and Jammy ** CVE removed: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2018-11803 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1970228 Title: Multiple vulnerabilities in Bionic, Focal and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1970228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973241] [NEW] Paramiko 2.9.0 breaks compatibility with devices only supporting ssh-rsa and not supporting server-sig-algs
Public bug reported:
[impact]
paramiko fails to connect to some servers.
[test case]
attempt to connect to a server that does not support server-sig-algs and
also only supports ssh-rsa (specifically, does not support rsa-
sha2-512). the connection will fail:
DEBUG:paramiko.transport:Finalizing pubkey algorithm for key of type 'ssh-rsa'
DEBUG:paramiko.transport:Our pubkey algorithm list: ['rsa-sha2-512',
'rsa-sha2-256', 'ssh-rsa']
DEBUG:paramiko.transport:Server did not send a server-sig-algs list; defaulting
to our first preferred algo ('rsa-sha2-512')
DEBUG:paramiko.transport:NOTE: you may use the 'disabled_algorithms'
SSHClient/Transport init kwarg to disable that or other algorithms if your
server does not support them!
INFO:paramiko.transport:Authentication (publickey) failed.
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/paramiko/client.py", line 435, in connect
self._auth(
File "/usr/lib/python3/dist-packages/paramiko/client.py", line 766, in _auth
raise saved_exception
File "/usr/lib/python3/dist-packages/paramiko/client.py", line 736, in _auth
key = self._key_from_filepath(
File "/usr/lib/python3/dist-packages/paramiko/client.py", line 588, in
_key_from_filepath
key = klass.from_private_key_file(key_path, password)
File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 249, in
from_private_key_file
key = cls(filename=filename, password=password)
File "/usr/lib/python3/dist-packages/paramiko/rsakey.py", line 64, in __init__
self._from_private_key_file(filename, password)
File "/usr/lib/python3/dist-packages/paramiko/rsakey.py", line 190, in
_from_private_key_file
data = self._read_private_key_file("RSA", filename, password)
File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 322, in
_read_private_key_file
data = self._read_private_key(tag, f, password)
File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 351, in
_read_private_key
data = self._read_private_key_openssh(lines[start:end], password)
File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 452, in
_read_private_key_openssh
raise PasswordRequiredException(
paramiko.ssh_exception.PasswordRequiredException: private key file is encrypted
[regression potential]
any regression would likely prevent paramiko from connecting to a remote
server.
[scope]
this needs to be fixed in jammy and later.
this problem was introduced in paramiko 2.9.0 so does not exist in
impish or earlier.
[other info]
this doesn't appear to be fixed upstream yet.
https://github.com/paramiko/paramiko/issues/2012
Note this can be worked around if direct access to the paramiko code is
possible, by using the 'disabled_algorithms' parameter to the client
connect() method, e.g.:
client.connect("", disabled_algorithms={'pubkeys': ['rsa-
sha2-256', 'rsa-sha2-512']})
Note this can break connections to other systems however, that do
support (only) those algs, so is not a very good workaround.
Additionally, this workaround isn't even possible if paramiko is being
used internally by some other python application.
** Affects: paramiko
Importance: Unknown
Status: Unknown
** Affects: paramiko (Ubuntu)
Importance: Undecided
Status: New
** Affects: paramiko (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: paramiko (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: paramiko (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: paramiko (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Bug watch added: github.com/paramiko/paramiko/issues #2012
https://github.com/paramiko/paramiko/issues/2012
** Also affects: paramiko via
https://github.com/paramiko/paramiko/issues/2012
Importance: Unknown
Status: Unknown
** Description changed:
[impact]
paramiko fails to connect to some servers.
[test case]
attempt to connect to a server that does not support server-sig-algs and
also only supports ssh-rsa (specifically, does not support rsa-
sha2-512). the connection will fail:
DEBUG:paramiko.transport:Finalizing pubkey algorithm for key of type 'ssh-rsa'
DEBUG:paramiko.transport:Our pubkey algorithm list: ['rsa-sha2-512',
'rsa-sha2-256', 'ssh-rsa']
DEBUG:paramiko.transport:Server did not send a server-sig-algs list;
defaulting to our first preferred algo ('rsa-sha2-512')
DEBUG:paramiko.transport:NOTE: you may use the 'disabled_algorithms'
SSHClient/Transport init kwarg to disable that or other algorithms if your
server does not support them!
INFO:paramiko.transport:Authentication (publickey) failed.
Traceback (most recent call last):
- File "", line 1, in
- File "/usr/lib/python3/dist-packages/paramiko/client.py", line 435, in
connect
- self._auth(
- File "/usr/lib/python3/dist-packages/paramiko/client.py", line 766, in _auth
- raise saved_exception
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
** No longer affects: cheese (Ubuntu Jammy) ** Changed in: clutter-gst-3.0 (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: clutter-gst-3.0 (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy
Packages patched for CVE-2020-35522, CVE-2022-0561, CVE-2022-0562, CVE-2022-0865 and CVE-2022-0891 are available for Bionic, Focal and Impish at https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa. (Impish is not affected by CVE-2020-35522.) Please patch the other CVEs and release a patched version for Jammy. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-35522 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971001 Title: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972735] Re: "go test archive/zip" fails, gophercolor16x16.png wrong size
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/golang-1.18/+git/golang-1.18/+merge/422246 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972735 Title: "go test archive/zip" fails, gophercolor16x16.png wrong size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.18/+bug/1972735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973107] Re: Failure to link a PIE binary on ppc64el (FTBFS)
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/golang-1.18/+git/golang-1.18/+merge/422246 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973107 Title: Failure to link a PIE binary on ppc64el (FTBFS) To manage notifications about this bug go to: https://bugs.launchpad.net/golang/+bug/1973107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970983] Re: failed to build against linux-unstable=5.18.0-1.1: CONFIG_VIDEO_V4L2 obsoleted
This bug was fixed in the package v4l2loopback - 0.12.5-1ubuntu6 --- v4l2loopback (0.12.5-1ubuntu6) kinetic; urgency=low * Check CONFIG_VIDEO_DEV against kernel version >= 5.18. (LP: #1970983) -- You-Sheng Yang Tue, 03 May 2022 03:55:33 + ** Changed in: v4l2loopback (Ubuntu Kinetic) 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/1970983 Title: failed to build against linux-unstable=5.18.0-1.1: CONFIG_VIDEO_V4L2 obsoleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1970983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973240] [NEW] Wireless mouse shows up under `lsusb` list but doesn't control the cursor
Public bug reported: What happens: Wireless mouse shows up under `lsusb` list but doesn't control the cursor. Expected behavior: The mouse controls the cursor. Background: I purchased a "Mini 2.4 GHz Wireless Optical Mini Finger Mouse Mice For Laptop PC Computers" (https://www.ebay.com/itm/283656756166) and plugged it into my laptop. Although this mouse appears under lsusb, it does not control the cursor. Other usb mice work, but not this one. Uniquely, this mouse uses a wireless dongle and some form of laser tracking, while my other peripherals are 'ordinary': a wired laster mouse and usb wired keyboard. Ubuntu version: ``` jacob:~/ $ lsb_release -rd [15:12:52] Description:Ubuntu 20.04.4 LTS Release:20.04 ``` lsusb (with not working, wireless mouse dongle inserted): ``` jacob:~/ $ lsusb [15:13:02] Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 016: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` lsusb (with no usb mouse): ``` jacob:~/ $ lsusb [15:13:44] Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` lsusb (with working, wired mouse): ``` jacob:~/ $ lsusb [15:14:32] Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 017: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` dmesg output: - no usb peripherals: [see attatched file `dmesg_no_peripherals.txt`] - wired mouse (works): [see attatched file `dmesg_wired_mouse.txt`] - wireless mouse (doesn't work): [see attatched file `dmesg_wireless_mouse.txt`] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178 Uname: Linux 5.4.0-109-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 12 14:58:18 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-107-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-109-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a8] Subsystem: Dell GM108M [GeForce 930MX] [1028:07a8] InstallationDate: Installed on 2020-11-03 (555 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 016: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 16, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 5: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: Dell Inc. Latitude 5580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-109-generic root=UUID=51015d56-7d65-470e-9290-eaa3eab354c5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.product.sku: 07A8 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Bug 1970989] Re: missing a tightly integrated deb package without snap
** Changed in: firefox (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970989 Title: missing a tightly integrated deb package without snap To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy
** Changed in: tiff (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971001 Title: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973237] Re: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade
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/1973237/+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/1973237 Title: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1973237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
** Also affects: xdg-utils (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: xdg-utils (Ubuntu Jammy) Status: New => Confirmed ** Changed in: xdg-utils (Ubuntu Jammy) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: xdg-utils (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/1970594 Title: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/1970594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972984] Re: Cannot paste filename into File Save dialog of Firefox Snap
I am linking to a GTK4 bug. I'm not sure if the GTK4 bug is the same as the xdg-desktop-portal-gnome issue but the GTK4 bug would need to be fixed first anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972984 Title: Cannot paste filename into File Save dialog of Firefox Snap To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1972984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972984] Re: Cannot paste filename into File Save dialog of Firefox Snap
Because this affects more than just Firefox, I am removing the Firefox task. I wasn't able to reproduce this bug if I did these steps: sudo apt uninstall xdg-desktop-portal-gnome Log out and log back in Now, snaps will use xdg-desktop-portal-gtk instead. Therefore, I believe this is a bug in either gtk4 or xdg-desktop-portal- gnome. And I don't believe it's a mutter bug. ** Package changed: firefox (Ubuntu) => xdg-desktop-portal-gnome (Ubuntu) ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided => Low ** Package changed: mutter (Ubuntu) => gtk4 (Ubuntu) ** Changed in: gtk4 (Ubuntu) Importance: Undecided => Low ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4905 https://gitlab.gnome.org/GNOME/gtk/-/issues/4905 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/4905 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972984 Title: Cannot paste filename into File Save dialog of Firefox Snap To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1972984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973230] Re: Merge php-twig 3.3.9-1 from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/php-twig/+git/php-twig/+merge/422244 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973230 Title: Merge php-twig 3.3.9-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-twig/+bug/1973230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970609] Re: Update xdg-desktop-portal-gnome to 42.1
** Description changed: Impact -- + This is a new stable release in the GNOME 42 series. - Test Case - - + It has one bugfix: an annoying error message that can be seen in apps like the Telegram snap when trying to save a file. + https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/29 + + + Test Case 1 + --- + snap install telegram-desktop + Open Telegram + Log in + Open a conversation with someone or a group. + Click one of the images that have been sent. + Click the save button to save it. It will automatically save the image to ~/Downloads/Telegram Desktop/ + + Test Case 2 + --- + snap install portal-test + Run the portal-test app and verify that things seem to work ok + + Test Case 3 + --- + Verify that you can open and save files with the Firefox and Chromium snaps What Could Go Wrong --- + xdg-desktop-portal-gnome provides critical functionality for snaps such as the filechooser for the browser apps. + + The Ubuntu flavors use a different portal backend, most commonly xdg- + desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. ** Also affects: xdg-desktop-portal-gnome (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: xdg-desktop-portal-gnome (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: xdg-desktop-portal-gnome (Ubuntu Jammy) Status: New => In Progress ** Description changed: Impact -- This is a new stable release in the GNOME 42 series. It has one bugfix: an annoying error message that can be seen in apps like the Telegram snap when trying to save a file. https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/29 - Test Case 1 --- snap install telegram-desktop Open Telegram Log in Open a conversation with someone or a group. Click one of the images that have been sent. - Click the save button to save it. It will automatically save the image to ~/Downloads/Telegram Desktop/ + Click the save button to save it. It will automatically save the image to ~/Downloads/Telegram Desktop/ without an error. Test Case 2 --- snap install portal-test Run the portal-test app and verify that things seem to work ok Test Case 3 --- Verify that you can open and save files with the Firefox and Chromium snaps What Could Go Wrong --- xdg-desktop-portal-gnome provides critical functionality for snaps such as the filechooser for the browser apps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970609 Title: Update xdg-desktop-portal-gnome to 42.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/1970609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973234] Re: Slow Boot, No SOUND, No Ethernet
Unfortunately, this command at terminal yields: mic@mic-Aspire-E5-576G:~$ apport-collect 1973234 ERROR: The python3-launchpadlib package is not installed. This functionality is not available. mic@mic-Aspire-E5-576G:~$ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973234 Title: Slow Boot, No SOUND, No Ethernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973237] [NEW] WiFi adapter, system speakers and brightness regulation stopped working after package upgrade
Public bug reported: After an unattended upgrade (the packages upgraded listed at the end), at least following things crashed: - WiFi adapter - not seen by the system - system speakers - not seen - cannot regulate the brightness of my laptop screen Used system:Ubuntu 18.04.6 LTS Release:18.04 version.log and lspci-vnvn.log in attachment --- upgraded and installed packages --- Start-Date: 2022-05-12 20:09:41 Commandline: /usr/bin/unattended-upgrade Upgrade: cron:amd64 (3.0pl1-128.1ubuntu1.1, 3.0pl1-128.1ubuntu1.2) End-Date: 2022-05-12 20:09:49 Start-Date: 2022-05-12 20:09:53 Commandline: /usr/bin/unattended-upgrade Upgrade: dnsmasq-base:amd64 (2.79-1ubuntu0.5, 2.79-1ubuntu0.6) End-Date: 2022-05-12 20:09:55 Start-Date: 2022-05-12 20:09:58 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:11 Start-Date: 2022-05-12 20:10:15 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox-locale-en:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:16 Start-Date: 2022-05-12 20:10:19 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox-locale-pl:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:20 Start-Date: 2022-05-12 20:10:24 Commandline: /usr/bin/unattended-upgrade Upgrade: libcurl3-gnutls:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18) End-Date: 2022-05-12 20:10:25 Start-Date: 2022-05-12 20:10:29 Commandline: /usr/bin/unattended-upgrade Upgrade: libnss3:amd64 (2:3.35-2ubuntu2.13, 2:3.35-2ubuntu2.14) End-Date: 2022-05-12 20:10:30 Start-Date: 2022-05-12 20:10:33 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-libc-dev:amd64 (4.15.0-176.185, 4.15.0-177.186) End-Date: 2022-05-12 20:10:34 Start-Date: 2022-05-12 20:10:38 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-signed-generic:amd64 (4.15.0.176.165, 4.15.0.177.166) End-Date: 2022-05-12 20:10:38 Start-Date: 2022-05-12 20:10:42 Commandline: /usr/bin/unattended-upgrade Upgrade: libcurl4:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18), curl:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18) End-Date: 2022-05-12 20:10:43 Start-Date: 2022-05-12 20:10:47 Commandline: /usr/bin/unattended-upgrade Install: linux-headers-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-image-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-headers-4.15.0-177:amd64 (4.15.0-177.186, automatic), linux-modules-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-modules-extra-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic) Upgrade: linux-headers-generic:amd64 (4.15.0.176.165, 4.15.0.177.166), linux-image-generic:amd64 (4.15.0.176.165, 4.15.0.177.166), linux-generic:amd64 (4.15.0.176.165, 4.15.0.177.166) End-Date: 2022-05-12 20:12:20 ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1973237/+attachment/5589334/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973237 Title: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1973237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973237] Re: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+bug/1973237/+attachment/5589335/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973237 Title: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1973237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942618] Re: package grub2-common 2.04-1ubuntu26.13 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942618 Title: package grub2-common 2.04-1ubuntu26.13 failed to install/upgrade: problemas de dependência - deixando desconfigurado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1942618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973234] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1973234 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973234 Title: Slow Boot, No SOUND, No Ethernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973028] Re: gnome-remote-desktop user service is always running
** Changed in: gnome-remote-desktop (Ubuntu) Status: Triaged => Fix Committed ** Description changed: Impact -- The gnome-remote-desktop systemd user service is always running. This was a contributing factor for LP: #1971415 Although it's "harmless" for the user service to be running if remote desktop sharing is not enabled, it's a waste of resources to run a service if it's not needed. Test Case - Install all Ubuntu updates and the gnome-remote-desktop update. From a clean install (or new user), run this command: systemctl --user status gnome-remote-desktop.service It should show the service as "Active: inactive" Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop. Use the systemctl command to verify that the service is "Active: active (running). Log out and log back in and reverify. Now turn off Remote Desktop Sharing and verify that the service is inactive. Log out and log back in and reverify. More details --- This fix uses a dpkg maintscript to remove /etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service . (That file is a symlink to the actual service). It also modifies debian/rules so that that file is no longer automatically added. Instead of /etc/systemd/user/ , the user service is intended to be enabled with the symlink ~/.config/systemd/user/gnome- session.target.wants/gnome-remote-desktop.service . That is appropriate since the GNOME implementation is per-user, not system-wide and it is also disabled by default. Fixing this bug has been strongly urged by the GNOME Remote Desktop maintainers, and this brings us in line with how non-Debian distros have been packaging gnome-remote-desktop. What could go wrong --- - The technical fix seems minimal, correct, and targeted to me. + The RDP and VNC sharing services in GNOME could start when they shouldn't or not start when they should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973028 Title: gnome-remote-desktop user service is always running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1973028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973232] Re: gnome-sound-recorder crashes at startup
** Package changed: gnome-media (Ubuntu) => gnome-sound-recorder (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973232 Title: gnome-sound-recorder crashes at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sound-recorder/+bug/1973232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973234] [NEW] Slow Boot, No SOUND, No Ethernet
Public bug reported: I would like to report the latest kernel update: 4.15.0.177.166 to my Linux Mint 19.1 systems displayed the following problems: 1. After Update - Boot process is VERY SLOW. 2. After Update - Once desktop comes up, mouse and keyboard are disabled for approx. 2 minutes. 3. All sound is totally disabled (gone) on the system and the device under Sound reports as "Dummy Output". 4. On another system with a USB-C to RJ45 Ethernet external connection dongle - the device was disabled, but could be re-detected, by removing and re-plugging into the USB-C port. This is not previously how it has operated. After having these issues on multiple machines, I restored the system(s) to the previous kernel 4.15.0-176-generic with Timeshift without issue, correcting all issues listed above. I believe this is a major issue(s) for the kernel and it's users and it needs to be addressed A.S.A.P. System Particulars: System:Host: mic-Aspire-E5-576G Kernel: 4.15.0-176-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.0.10 wm: muffin 4.0.7 dm: LightDM 1.26.0 Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: Mobo: KBL model: Ironman_SK v: V1.47 serial: UEFI: Insyde v: 1.47 date: 09/06/2018 Battery: ID-1: BAT1 charge: 34.3 Wh condition: 34.3/62.2 Wh (55%) volts: 12.7/11.1 model: PANASONIC AS16B5J type: Li-ion serial: status: Full Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 serial: charge: 100% rechargeable: yes status: Discharging CPU: Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 6144 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 700 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 700 2: 700 3: 700 4: 709 5: 706 6: 700 7: 720 8: 700 Graphics: Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5917 Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI driver: N/A bus ID: 01:00.0 chip ID: 10de:1d10 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71 Sound Server: ALSA v: k4.15.0-176-generic Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: 4000 bus ID: 03:00.0 chip ID: 8086:24fb IF: wlp3s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI driver: r8169 v: 2.3LK-NAPI port: 3000 bus ID: 04:00.1 chip ID: 10ec:8168 IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 912.89 GiB used: 172.01 GiB (18.8%) ID-1: /dev/sda vendor: SanDisk model: Ultra II 480GB size: 447.13 GiB speed: 6.0 Gb/s serial: rev: 20RL scheme: GPT ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD4 size: 465.76 GiB speed: 6.0 Gb/s serial: rev: 023 scheme: MBR Partition: ID-1: / size: 438.62 GiB used: 113.17 GiB (25.8%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 46.5 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/alex-p-aegisub-bionic.list 1: deb http://ppa.launchpad.net/alex-p/aegisub/ubuntu bionic main 2: deb-src http://ppa.launchpad.net/alex-p/aegisub/ubuntu bionic main Active apt repos in: /etc/apt/sources.list.d/audio-recorder-ppa-bionic.list 1: deb http://ppa.launchpad.net/audio-recorder/ppa/ubuntu bionic main 2: deb-src http://ppa.launchpad.net/audio-recorder/ppa/ubuntu bionic main Active apt repos in: /etc/apt/sources.list.d/clipgrab-team-ppa-bionic.list 1: deb http://ppa.launchpad.net/clipgrab-team/ppa/ubuntu bionic main 2: deb-src http://ppa.launchpad.net/clipgrab-team/ppa/ubuntu bionic main Active apt repos in: /etc/apt/sources.list.d/gezakovacs-ppa-bionic.list 1: deb http://ppa.launchpad.net/gezakovacs/ppa/ubuntu bionic main 2: deb-src http://ppa.launchpad.net/gezakovacs/ppa/ubuntu bionic main Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
This bug may be mutter/wayland related as the player seems to work in xorg but not wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873923] Re: freeradius with freeradius-python3 fails to start out of the box
Focal verification Problem reproduced with focal packages 3.0.20+dfsg-3build1 May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: Python version: 3.8.10 (default, Mar 15 2022, 12:22:08) [GCC 9.4.0] May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: Libpython is not found among linked libraries May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: Failed loading libpython symbols into global symbol table May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: *** example.py instantiate *** May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: rlm_cache (cache_eap): Driver rlm_cache_rbtree (module rlm_cache_rbtree) loaded and linked May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: Ignoring "sql" (see raddb/mods-available/README.rst) May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: Ignoring "ldap" (see raddb/mods-available/README.rst) May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: # Skipping contents of 'if' as it is always 'false' -- /etc/freeradius/3.0/sites-enabled/inner-tunnel:336 May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: radiusd: Skipping IP addresses and Ports May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: Configuration appears to be OK May 12 19:05:28 focal-freeradius-1873923 freeradius[3976]: *** example.py detach *** May 12 19:05:28 focal-freeradius-1873923 systemd[1]: freeradius.service: Control process exited, code=dumped, status=11/SEGV Installing updated packages from proposed: ubuntu@focal-freeradius-1873923:~$ apt-cache policy freeradius-python3 freeradius-python3: Installed: 3.0.20+dfsg-3ubuntu0.1 Candidate: 3.0.20+dfsg-3ubuntu0.1 Version table: *** 3.0.20+dfsg-3ubuntu0.1 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 3.0.20+dfsg-3build1 500 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages This time, service restarts fine: ubuntu@focal-freeradius-1873923:~$ sudo systemctl restart freeradius ubuntu@focal-freeradius-1873923:~$ ubuntu user test passes: ubuntu@focal-freeradius-1873923:~$ radtest ubuntu anypass 127.0.0.1 0 testing123 Sent Access-Request Id 220 from 0.0.0.0:54648 to 127.0.0.1:1812 length 76 User-Name = "ubuntu" User-Password = "anypass" NAS-IP-Address = 10.0.100.10 NAS-Port = 0 Message-Authenticator = 0x00 Cleartext-Password = "anypass" Received Access-Accept Id 220 from 127.0.0.1:1812 to 127.0.0.1:54648 length 35 Reply-Message = "Hello ubuntu!" A non-ubuntu user is rejected as expected: ubuntu@focal-freeradius-1873923:~$ radtest anotheruser neverworks 127.0.0.1 0 testing123 Sent Access-Request Id 150 from 0.0.0.0:57202 to 127.0.0.1:1812 length 81 User-Name = "anotheruser" User-Password = "neverworks" NAS-IP-Address = 10.0.100.10 NAS-Port = 0 Message-Authenticator = 0x00 Cleartext-Password = "neverworks" Received Access-Reject Id 150 from 127.0.0.1:1812 to 127.0.0.1:57202 length 41 Reply-Message = "You are not ubuntu!" (0) -: Expected Access-Accept got Access-Reject Focal verification succeeded. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873923 Title: freeradius with freeradius-python3 fails to start out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1873923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
Has anybody encountered this recently when upgrading a fully update to date Focal system to Jammy? ** Changed in: dbus (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968845 Title: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
This bug was fixed in the package xdg-utils - 1.1.3-4.1ubuntu2 --- xdg-utils (1.1.3-4.1ubuntu2) kinetic; urgency=medium * Cherry-pick an upstream merge request to remove bashisms from xdg-settings (LP: #1970594) - debian/source/options - debian/patches/upstream-mr-remove-bashisms.patch -- Olivier Tilloy Tue, 03 May 2022 11:16:46 +0200 ** Changed in: xdg-utils (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/1970594 Title: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/1970594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
I did some tests, and looks like I was able to configure ubuntu 22.04 to export NFS v2. I was able to mount from an ubuntu 14.04 machine specifying vers=2: t1 is trusty (14.04), j1 is jammy (22.04): root@t1:~# rpcinfo -s j1-nfs-server program version(s) netid(s) service owner 10 2,3,4 local,udp,tcp,udp6,tcp6 portmapper superuser 100024 1 tcp6,udp6,tcp,udpstatus 113 15 3,2,1 tcp6,udp6,tcp,udpmountd superuser 13 4,3,2 tcp6,tcp nfs superuser 100227 3,2 tcp6,tcp - superuser 100021 4,3,1 tcp6,udp6,tcp,udpnlockmgrsuperuser root@t1:~# mount j1-nfs-server:/storage /mnt -o vers=2 root@t1:~# mount -t nfs j1-nfs-server:/storage on /mnt type nfs (rw,vers=2,addr=192.168.122.136) Note that TCP was used, though, not UDP. To allow the 22.04 server to export via UDP, add "udp=y" to the [nfsd] section in /etc/nfs.conf and restart nfs-utils and nfs-server, and then I can specify udp: root@t1:~# mount j1-nfs-server:/storage /mnt -o vers=2,udp j1-nfs-server:/storage on /mnt type nfs (rw,vers=2,udp,addr=192.168.122.136) The config I used on the 22.04 server was: root@j1-nfs-server:~# nfsconf --dump [general] pipefs-directory = /run/rpc_pipefs [mountd] manage-gids = 1 [nfsd] debug = all rdma = n threads = 8 udp = y vers2 = y vers2,3,4 = y vers3 = y vers4 = y vers4.0 = y vers4.1 = y vers4.2 = y That being said, from 22.04 I CANNOT mount an NFSv2 export: root@j1-nfs-server:~# mount j1-nfs-server:/storage /mnt -o vers=2 mount.nfs: requested NFS version or transport protocol is not supported So the TL:DR seems to be that 22.04 can export NFSv2, even via UDP, but not MOUNT NFSv2. To make progress in this bug, please show: - nfsconf --dump on the 22.04 server - attempted mount error on the NFSv2 and NFSv3 clients, including dmesg and /var/log/syslog (or equivalent) covering the attempt - try enabling UDP in your 22.04 server's /etc/nfs.conf. Keep in mind that, since your server was upgraded, you will also have an /etc/nfs.conf.d/local.conf. You may want to merge local.conf with nfs.conf. See the release notes at [1] for more details, and perhaps the server guide[2] where the new nfs changes are also documented, in particular the upgrade scenario. 1. https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668 2. https://ubuntu.com/server/docs/service-nfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
