[Bug 1913530] Re: Getting seg-fault while playing any stream through vlc with HW accelerated decoder in Jetson platform
Hey Rémi, thanks for the fix, it will solve our issue, may I know when it will be released? is it already upstreamed or is it going to be in some time? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913530 Title: Getting seg-fault while playing any stream through vlc with HW accelerated decoder in Jetson platform To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1913530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: ubuntu-z-systems 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/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909428] Re: eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with unexpected operator on F-5.8
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909428 Title: eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with unexpected operator on F-5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914574] Re: [21.04 FEAT] Upgrade s390-tools to latest version (2.16.0)
** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914574 Title: [21.04 FEAT] Upgrade s390-tools to latest version (2.16.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916670] Re: sddm-greeter crashes with segfault (Bad RIP value) before login shows up on Lubuntu 20.04.2 LTS
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1916670 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916670 Title: sddm-greeter crashes with segfault (Bad RIP value) before login shows up on Lubuntu 20.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1916670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916708] Re: udpif_revalidator crash in ofpbuf_resize__
E-mailed upstream for assistance: https://mail.openvswitch.org/pipermail/ovs-discuss/2021-February/050963.html ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916708 Title: udpif_revalidator crash in ofpbuf_resize__ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1916708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916708] [NEW] udpif_revalidator crash in ofpbuf_resize__
Public bug reported: The udpif_revalidator thread crashed in ofpbuf_resize__ on openvswitch 2.9.2-0ubuntu0.18.04.3~cloud0 (on 16.04 from the xenial-queens cloud archive, backported from the 18.04 release of the same version). Kernel version was 4.4.0-159-generic. The issue is suspected to still exist in upstream master as Feb 2021/v2.15.0 but has not been completed understood. Opening this bug to track future occurances. The general issue appears to be that the udpif_revaliditator thread tried to expand a stack-allocated ofpbuf to fit a netlink reply with size 3204 but the buffer is of size 2048. This intentionally raises an assertion as we can't expand the memory on the stack. The crash in __ofpbuf_resize__ appears due to OVS_NOT_REACHED() being called because b->source = OFPBUF_STACK (the line number indicates it's the default: case but this appears to be an optimiser quirk, b->source is OFPBUF_STACK). We can't realloc() the buffer memory if it's allocated on the stack. This buffer is provided in #7 nl_sock_transact_multiple__ during the call to nl_sock_recv__, specified as buf_txn->reply. In this specific case it seems we found transactions[0] available and so we used that rather than tmp_txn. The original source of transactions (it's passed through most of the function calls) appears to be op_auxdata allocated on the stack at the top of the dpif_netlink_operate__ function (dpif-netlink.c:1875). The size of this particular message was 3204, so 2048 went into the buffer and 1156 went into the tail iovector setup inside nl_sock_recv__ which it then tried to expand the ofpbuf to hold. Various nl_sock_* functions have comments about the buffer ideally being the right size for optimal performance (I guess to avoid the reallocation), but it seems like a possible oversight in the dpif_netlink_operate__ workflow that the nl_sock_* functions may ultimately want to try to expand that buffer and then fail because of the stack allocation. The relevant source tree can be found here: git clone -b applied/2.9.2-0ubuntu0.18.04.3 https://git.launchpad.net/ubuntu/+source/openvswitch https://git.launchpad.net/ubuntu/+source/openvswitch/tree/?h=applied/2.9.2-0ubuntu0.18.04.3 Thread 1 (Thread 0x7f3e0700 (LWP 1539131)): #0 0x7f3ed30c8428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x7f3ed30ca02a in __GI_abort () at abort.c:89 #2 0x004e5035 in ofpbuf_resize__ (b=b@entry=0x7f3e0fffb050, new_headroom=, new_tailroom=new_tailroom@entry=1156) at ../lib/ofpbuf.c:262 #3 0x004e5338 in ofpbuf_prealloc_tailroom (b=b@entry=0x7f3e0fffb050, size=size@entry=1156) at ../lib/ofpbuf.c:291 #4 0x004e54e5 in ofpbuf_put_uninit (size=size@entry=1156, b=b@entry=0x7f3e0fffb050) at ../lib/ofpbuf.c:365 #5 ofpbuf_put (b=b@entry=0x7f3e0fffb050, p=p@entry=0x7f3e0ffcf0a0, size=size@entry=1156) at ../lib/ofpbuf.c:388 #6 0x005392a6 in nl_sock_recv__ (sock=sock@entry=0x7f3e50009150, buf=0x7f3e0fffb050, wait=wait@entry=false) at ../lib/netlink-socket.c:705 #7 0x00539474 in nl_sock_transact_multiple__ (sock=sock@entry=0x7f3e50009150, transactions=transactions@entry=0x7f3e0ffdff20, n=1, done=done@entry=0x7f3e0ffdfe10) at ../lib/netlink-socket.c:824 #8 0x0053980a in nl_sock_transact_multiple (sock=0x7f3e50009150, transactions=transactions@entry=0x7f3e0ffdff20, n=n@entry=1) at ../lib/netlink-socket.c:1009 #9 0x0053aa1b in nl_sock_transact_multiple (n=1, transactions=0x7f3e0ffdff20, sock=) at ../lib/netlink-socket.c:1765 #10 nl_transact_multiple (protocol=protocol@entry=16, transactions=transactions@entry=0x7f3e0ffdff20, n=n@entry=1) at ../lib/netlink-socket.c:1764 #11 0x00528b01 in dpif_netlink_operate__ (dpif=dpif@entry=0x25a6150, ops=ops@entry=0x7f3e0fffaf28, n_ops=n_ops@entry=1) at ../lib/dpif-netlink.c:1964 #12 0x00529956 in dpif_netlink_operate_chunks (n_ops=1, ops=0x7f3e0fffaf28, dpif=) at ../lib/dpif-netlink.c:2243 #13 dpif_netlink_operate (dpif_=0x25a6150, ops=, n_ops=) at ../lib/dpif-netlink.c:2279 #14 0x004756de in dpif_operate (dpif=0x25a6150, ops=, ops@entry=0x7f3e0fffaf28, n_ops=n_ops@entry=1) at ../lib/dpif.c:1359 #15 0x004758e7 in dpif_flow_get (dpif=, key=, key_len=, ufid=, pmd_id=, buf=buf@entry=0x7f3e0fffb050, flow=) at ../lib/dpif.c:1014 #16 0x0043f662 in ukey_create_from_dpif_flow (udpif=0x229cbf0, udpif=0x229cbf0, ukey=, flow=0x7f3e0fffc790) at ../ofproto/ofproto-dpif-upcall.c:1709 #17 ukey_acquire (error=, result=, flow=0x7f3e0fffc790, udpif=0x229cbf0) at ../ofproto/ofproto-dpif-upcall.c:1914 #18 revalidate (revalidator=0x250eaa8) at ../ofproto/ofproto-dpif-upcall.c:2473 #19 0x0043f816 in udpif_revalidator (arg=0x250eaa8) at ../ofproto/ofproto-dpif-upcall.c:913 #20 0x004ea4b4 in ovsthread_wrapper (aux_=) at ../lib/ovs-thread.c:348 #21 0x7f3ed39756ba in start_thread (arg=0x7f3e0700) at pthread_create.c:333 #22 0x7f3ed319a41d in
[Bug 1887933] Re: [21.04 FEAT] wireshark: Update to include SMC support
Over night I've also did a PPA test build that's available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1887933 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887933 Title: [21.04 FEAT] wireshark: Update to include SMC support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912789] Re: Add support for selective build of special drivers
Resetting back to pending to reflect the required fixup. ** Changed in: linux (Ubuntu Focal) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912789 Title: Add support for selective build of special drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1915870] Re: gnome session not starting (segfault with r300_dri.so)
Hi Mark,Where do I find the "patch.diff"? Thanks,Santosh- Sent from a web-browser based mail client! On Wednesday, February 24, 2021, 02:30:55 AM GMT+5:30, Mark Muth <1915...@bugs.launchpad.net> wrote: Now I can confirm, applying the patch mentioned above brings my PC back to normal. Short summary for everyone else who might read this bug report: Download and save patch as patch.diff and run: sudo apt-build install --patch patch.diff libgl1-mesa-dri -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1915870 Title: gnome session not starting (segfault with r300_dri.so) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916462] Re: dnsmasq failed to send packet: Network is unreachable
Confirmed: with the updated package, the reported problem no longer exists. Please make that release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916462 Title: dnsmasq failed to send packet: Network is unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1916462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
It looks like this glib error always comes first: Feb 24 15:24:48 kab gnome-shell[1013]: invalid (NULL) pointer instance Feb 24 15:24:48 kab gnome-shell[1013]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed ... Feb 24 15:25:39 kab gnome-shell[1013]: JS ERROR: Gio.IOErrorEnum: Error calling StartServiceByName for org.gnome.SessionManager: Timeout was reached -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
When the login screen does finally come up (without Wayland support), the first log message is: Feb 24 15:25:39 kab gnome-shell[1013]: JS ERROR: Gio.IOErrorEnum: Error calling StartServiceByName for org.gnome.SessionManager: Timeout was reached _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:290:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:267:17 SessionManager@resource:///org/gnome/shell/misc/gnomeSession.js:36:12 _init@resource:///org/gnome/shell/misc/systemActions.js:140:25 getDefault@resource:///org/gnome/shell/misc/systemActions.js:28:22 _init@resource:///org/gnome/shell/ui/status/system.js:18:31 _init@resource:///org/gnome/shell/ui/panel.js:743:24 _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1070:25 _updateBox@resource:///org/gnome/shell/ui/panel.js:1081:34 _updatePanel@resource:///org/gnome/shell/ui/panel.js:1027:14 _init@resource:///org/gnome/shell/ui/panel.js:836:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:221:13 start@resource:///org/gnome/shell/ui/main.js:162:5 @:1:47 Feb 24 15:25:39 kab gnome-shell[1013]: Execution of main.js threw exception: Script threw an exception -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887933] Re: [21.04 FEAT] wireshark: Update to include SMC support
** Changed in: ubuntu-z-systems Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887933 Title: [21.04 FEAT] wireshark: Update to include SMC support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915717] Re: Ubuntu 21.04, kernel feature request, TLS device offload for Bond
Hi, I retried and All 8 commits were cleanly applied above tag: Ubuntu-unstable-5.11.0-10.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915717 Title: Ubuntu 21.04, kernel feature request, TLS device offload for Bond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916570] Re: BlueZ 5.56 release
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916570 Title: BlueZ 5.56 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1916570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916705] [NEW] glib2.0 >=2.67.3 breaks include from an extern C context
Public bug reported:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
from /usr/include/glib-2.0/glib/gtypes.h:32,
from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
56 | template
| ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
20 | extern "C" {
| ^~
Also in disas/nanomips.cpp, ...
And indeed disas/arm-a64.cc has:
20 extern "C" {
21 #include "qemu/osdep.h"
22 #include "disas/dis-asm.h"
23 }
Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.
So C++ constructs within a C scope which is this bug.
Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.
But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...
It is indeed failing in -proposed but working in hirsute-release.
10.2.1-20ubuntu1 : bad
repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp
With that I have a test env...
Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
It must be something else.
The difference were ~340 packages I was upgrading them to spot what broke it.
I eventually found glib 2.66 -> 2.67 to break it.
libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
Old:
/*
* We can only use __typeof__ on GCC >= 4.8, and not when compiling C++. Since
* __typeof__ is used in a few places in GLib, provide a pre-processor symbol
* to factor the check out from callers.
*
* This symbol is private.
*/
#undef g_has_typeof
#if defined(__GNUC__) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >=
8)) && !defined(__cplusplus)
#define g_has_typeof
#endif
New:
/*
* We can only use __typeof__ on GCC >= 4.8, and not when compiling C++. Since
* __typeof__ is used in a few places in GLib, provide a pre-processor symbol
* to factor the check out from callers.
*
* This symbol is private.
*/
#undef glib_typeof
#if !defined(__cplusplus) && \
((defined(__GNUC__) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__
[Bug 1384122] Re: SNMPD defaultmonitors not working
Hello @paride, I am observing the same problem in Net-snmp version 5.8 with OpenWRT. root@OpenWrt:~# snmpd -DALL -Lo -c /etc/config/snmpd.conf & root@OpenWrt:~# buffer too small to read octet string (11 < 11) Turning on AgentX master support. /etc/config/snmpd.conf: line 21: Warning: Unknown token: iquerySecName. /etc/config/snmpd.conf: line 23: Warning: Unknown token: linkUpDownNotifications. NET-SNMP version 5.8 It would be very helpful if you can provide a patch for OpenWRT or even a workaround. Thanks in advance, Nisha -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384122 Title: SNMPD defaultmonitors not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1384122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916468] Re: powerpc/eeh-basic.sh in kselftest make P8 node stopped working
https://lists.ubuntu.com/archives/kernel-team/2021-February/117502.html ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916468 Title: powerpc/eeh-basic.sh in kselftest make P8 node stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1916468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916701] [NEW] [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
Public bug reported: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). ** Affects: glib2.0 (Ubuntu) Importance: Critical Status: New ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute regression-proposed ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789177] Re: RabbitMQ fails to synchronize exchanges under high load
With 2nd try, I also faced the same error with patched component, not even only openvswitch-agent. I'm going to try to reproduce with 1st and 3rd commit with manual configuration( enable_cancel_on_failover) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789177 Title: RabbitMQ fails to synchronize exchanges under high load To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887933] Re: [21.04 FEAT] wireshark: Update to include SMC support
** Information type changed from Private to Public ** Changed in: wireshark (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887933 Title: [21.04 FEAT] wireshark: Update to include SMC support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
** Changed in: clucene-core (Ubuntu) Status: Triaged => In Progress ** Changed in: clucene-core (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915870] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
** Summary changed: - gnome session not starting (segfault in r300_dri.so) + gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916463] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
*** This bug is a duplicate of bug 1915870 *** https://bugs.launchpad.net/bugs/1915870 ** Summary changed: - gnome-session-check-accelerated-gl-helper crashed with SIGSEGV + gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] ** This bug has been marked a duplicate of bug 1915870 gnome session not starting (segfault in r300_dri.so) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916463 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1916463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872870] Re: Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Yes I acknowledge you've attempted to by adding gif & video evidence, however the bug has been reported on a package that was created 2019-October-18 and has received no updates since then, so what 'update' are you referring to? More specific details are needed. It's very likely you've filed against an incorrect package, however too few details exist in the initial bug report for the issue to be identified, as what the 'update' was will be key. 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/1872870 Title: Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
** Changed in: oem-priority Status: Fix Committed => Fix Released ** Changed in: oem-priority/bionic Status: Fix Committed => Fix Released ** Changed in: oem-priority/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/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: s390-tools (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914574] Re: [21.04 FEAT] Upgrade s390-tools to latest version (2.16.0)
** Changed in: s390-tools (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914574 Title: [21.04 FEAT] Upgrade s390-tools to latest version (2.16.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
Ok I've sent a message at https://01.org/ asking for more help or directions stating you need more hardware information! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
I've already tried reaching out to Dell's customer support (https://community.intel.com/t5/Processors/No-HDMI-output-using-Linux- Mint/m-p/1244240#M48905), but they replied with: "Please be aware that Intel does not provide direct downloads and technical support for Linux drivers. The Intel Graphics Linux driver is primarily supported through the original equipment manufacturer (OEM), the Linux distribution vendor, or by the Intel Open Source Technology Center at https://01.org/linuxgraphics.; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789177] Re: RabbitMQ fails to synchronize exchanges under high load
after restarting all rabbitmq-server, status are stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789177 Title: RabbitMQ fails to synchronize exchanges under high load To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916468] Re: powerpc/eeh-basic.sh in kselftest make P8 node stopped working
** Description changed:
- Issue found on node entei with Focal kernel.
+ [Impact]
+ When trying to run this test on P8 node entei with Focal kernel, it will try
to break 4 devices on Focal, and one of them is using the AHCI driver:
- When trying to run this test, it will try to break 4 devices on Focal,
- and one of them is using the AHCI driver:
-
- $ sudo ./eeh-basic.sh
+ $ sudo ./eeh-basic.sh
:00:00.0, Skipped: bridge
0001:00:00.0, Skipped: bridge
0020:00:00.0, Skipped: bridge
0021:00:00.0, Skipped: bridge
0021:01:00.0, Skipped: bridge
0021:02:01.0, Skipped: bridge
0021:02:08.0, Skipped: bridge
0021:02:09.0, Skipped: bridge
0021:02:0a.0, Skipped: bridge
0021:02:0b.0, Skipped: bridge
0021:02:0c.0, Skipped: bridge
0021:0d:00.0, Added
0021:0e:00.0, Added
0021:0f:00.0, Skipped: bridge
0021:10:00.0, Added
0022:00:00.0, Skipped: bridge
0022:01:00.0, Added
Found 4 breakable devices...
Breaking 0021:0d:00.0...
0021:0d:00.0, waited 0/60
0021:0d:00.0, waited 1/60
0021:0d:00.0, waited 2/60
0021:0d:00.0, waited 3/60
0021:0d:00.0, waited 4/60
0021:0d:00.0, waited 5/60
0021:0d:00.0, waited 6/60
0021:0d:00.0, waited 7/60
0021:0d:00.0, waited 8/60
0021:0d:00.0, Recovered after 9 seconds
Breaking 0021:0e:00.0...
0021:0e:00.0, waited 0/60
0021:0e:00.0, waited 1/60
./eeh-basic.sh: 74: sleep: Input/output error
0021:0e:00.0, waited 2/60
./eeh-basic.sh: 74: sleep: Input/output error
- 0021:0e:00.0, waited 3/60
- ./eeh-basic.sh: 74: sleep: Input/output error
./eeh-basic.sh: 74: sleep: Input/output error
0021:0e:00.0, waited 59/60
./eeh-basic.sh: 74: sleep: Input/output error
0021:0e:00.0, waited 60/60
./eeh-basic.sh: 74: sleep: Input/output error
0021:0e:00.0, Failed to recover!
Breaking 0021:10:00.0...
Skipping 0021:10:00.0, Initial PE state is not ok
Breaking 0022:01:00.0...
Skipping 0022:01:00.0, Initial PE state is not ok
3 devices failed to recover (4 tested)
./eeh-basic.sh: 81: lspci: Input/output error
./eeh-basic.sh: 81: diff: Input/output error
./eeh-basic.sh: 82: rm: Input/output error
./eeh-basic.sh: 84: test: 3: unexpected operator
With the driver failed to recovery, the system will start acting up.
$ ls
ls: command not found
- And drop into read-only state, dmesg can be found in the attachment.
+ And drop into a read-only state
+
+ [Fixes]
+ * bbe9064f30f06e ("selftests/eeh: Skip ahci adapters")
+
+ This is only affecting Focal and it can be cherry-picked.
+
+ [Test case]
+ Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/ on the
affected P8 node, the test should pass without any issue.
+
+ [Where problems could occur]
+ This fix is limited to PowerPC testing tool, it should not cause any issue.
** Description changed:
- [Impact]
- When trying to run this test on P8 node entei with Focal kernel, it will try
to break 4 devices on Focal, and one of them is using the AHCI driver:
+ [Impact]
+ When trying to run this test on P8 node entei with Focal kernel, it will try
to break 4 devices on Focal, and one of them is using the AHCI driver which
doesn't support error recovery:
$ sudo ./eeh-basic.sh
:00:00.0, Skipped: bridge
0001:00:00.0, Skipped: bridge
0020:00:00.0, Skipped: bridge
0021:00:00.0, Skipped: bridge
0021:01:00.0, Skipped: bridge
0021:02:01.0, Skipped: bridge
0021:02:08.0, Skipped: bridge
0021:02:09.0, Skipped: bridge
0021:02:0a.0, Skipped: bridge
0021:02:0b.0, Skipped: bridge
0021:02:0c.0, Skipped: bridge
0021:0d:00.0, Added
0021:0e:00.0, Added
0021:0f:00.0, Skipped: bridge
0021:10:00.0, Added
0022:00:00.0, Skipped: bridge
0022:01:00.0, Added
Found 4 breakable devices...
Breaking 0021:0d:00.0...
0021:0d:00.0, waited 0/60
0021:0d:00.0, waited 1/60
0021:0d:00.0, waited 2/60
0021:0d:00.0, waited 3/60
0021:0d:00.0, waited 4/60
0021:0d:00.0, waited 5/60
0021:0d:00.0, waited 6/60
0021:0d:00.0, waited 7/60
0021:0d:00.0, waited 8/60
0021:0d:00.0, Recovered after 9 seconds
Breaking 0021:0e:00.0...
0021:0e:00.0, waited 0/60
0021:0e:00.0, waited 1/60
./eeh-basic.sh: 74: sleep: Input/output error
0021:0e:00.0, waited 2/60
./eeh-basic.sh: 74: sleep: Input/output error
./eeh-basic.sh: 74: sleep: Input/output error
0021:0e:00.0, waited 59/60
./eeh-basic.sh: 74: sleep: Input/output error
0021:0e:00.0, waited 60/60
./eeh-basic.sh: 74: sleep: Input/output error
0021:0e:00.0, Failed to recover!
Breaking 0021:10:00.0...
Skipping 0021:10:00.0, Initial PE state is not ok
Breaking 0022:01:00.0...
Skipping 0022:01:00.0, Initial PE state is not ok
3 devices failed to recover (4 tested)
./eeh-basic.sh: 81: lspci: Input/output error
./eeh-basic.sh: 81: diff: Input/output error
./eeh-basic.sh: 82: rm: Input/output error
./eeh-basic.sh: 84: test: 3: unexpected operator
With the driver failed to recovery, the system will start acting up.
$ ls
ls: command
[Bug 1906236] Re: Intel Thunderbolt 4 Maple Ridge support
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906236 Title: Intel Thunderbolt 4 Maple Ridge support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
Based on your result, the hardware also can't work with Intel's development branch, then the Ubuntu's kernel doesn't work for you as expect. I have verified on two certified hardwares. https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202006-27982/ The HDMI output works both on oem kernel 5.6 and 5.10. It seems I can't reproduce your problem, but your hardware config is a bit different from what I have in hand. Could you file a bug to Dell customer support? They will provide me the hardware if they expect the hardware can work with open platform. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916468] Re: powerpc/eeh-basic.sh in kselftest make P8 node stopped working
Hi Guilherme, yes this should be skipped in the test. Thanks ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1916468 Title: powerpc/eeh-basic.sh in kselftest make P8 node stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1916468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916120] Re: Can not install podman and buildah together
Installation works now. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916120 Title: Can not install podman and buildah together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1916120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916468] Re: powerpc/eeh-basic.sh in kselftest make P8 node stopped working
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916468 Title: powerpc/eeh-basic.sh in kselftest make P8 node stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1916468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789177] Re: RabbitMQ fails to synchronize exchanges under high load
1. deploy rocky 2. installed updated oslo.messaging pkg in below nodes - neutron-api - neutron-gateway - nova-compute - - restarted openvswitch-agent only 3. tried to reproduce with below config - created 3000 test queue, exchange, bindings - juju config rabbitmq-server min-cluster-size=1 - juju config rabbitmq-server connection-backlog=200 ( to make all rabbitmq-server restart ) - shutdown node with maas controller ( one of rabbitmq-server) - power on with maas controller I'm able to see Channel not found error for nova, and for neutron-openvswitch-agent on nova-compute node. neutron-openvswitch-agent on nova-compute node has fixed but rabbitmq-server shows me channel not found error. However, I can't launch and delete instance on this environment. I'm not sure how to say about this result. Also reproduction itself is quite hard to make. It took a lot of time to find regular behavior but I'm not sure there is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789177 Title: RabbitMQ fails to synchronize exchanges under high load To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908991] Re: Compose key doesn't work after a while
I configure the key on GNOME tweaks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908991 Title: Compose key doesn't work after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908991] Re: Compose key doesn't work after a while
The kernel config used for my custom kernels is roughly same as official Ubuntu kernel. The first time I compile the kernel, it is based on official kernel config, then on subsequent custom kernel updates I simply run `make olddefconfig`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908991 Title: Compose key doesn't work after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916690] [NEW] git clone --filter is undocumented, although the option is present
Public bug reported: Git on Ubuntu Focal (v2.25) have --filter option, however it is undocumented. The upstream commit 4a465443a6ce51bd6e1d4ffef56d3f2e8d45f506 add that documentation. The commit is available as attached patch. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: git 1:2.25.1-1ubuntu3 Uname: Linux 5.10.11-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 24 12:07:12 2021 InstallationDate: Installed on 2020-05-05 (294 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: git UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 ** Affects: git (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Patch added: "upstream patch" https://bugs.launchpad.net/bugs/1916690/+attachment/5466382/+files/0001-clone-document-filter-options.patch ** Description changed: Git on Ubuntu Focal (v2.25) have --filter option, however it is undocumented. The upstream commit 4a465443a6ce51bd6e1d4ffef56d3f2e8d45f506 add that documentation. The - commit is available as attached patch below. + commit is available as attached patch. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: git 1:2.25.1-1ubuntu3 Uname: Linux 5.10.11-kernelorg-upstream-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 24 12:07:12 2021 InstallationDate: Installed on 2020-05-05 (294 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: git UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-08-11T18:33:58.913741 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916690 Title: git clone --filter is undocumented, although the option is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1916690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914456] Re: 120 sec kernel timeout is seen during SCSI remove_device.
Hi Guilherme, Here is the update from my side. 1. sosreport command hung at below message, Setting up archive ... Setting up plugins ... Running plugins. Please wait ... Finishing plugins [Running: block btrfs] Plugin block timed out Plugin btrfs timed out 2. Automation test is long running test that perform below operations in sequence for infinite iterations. a. Create bunch of iSCSI LUNs. b. Discover LUNs through sysfs scan c. Format LUNs d. Perform IO e. Remove LUN f. Delete LUN 3. It takes couple of days to reproduce the issue and its not 100% reproducible. 4. Currently system is in repro state. So I would like to request, If it is possible to get onto WebEx and collect specific information from system? I would like to capture as much info as possible before trying another repro attempt. Thanks for the support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914456 Title: 120 sec kernel timeout is seen during SCSI remove_device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1914456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882503] Re: eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4 P8 / P9
** Changed in: ubuntu-kernel-tests 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/1882503 Title: eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4 P8 / P9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Groovy) 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/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914411] Re: Fix broken efifb on graphics device without driver
https://cgit.freedesktop.org/drm/drm- misc/commit/?id=a6c0fd3d5a8bac08b0d79301be23f961e9038d60 in drm-misc- next the day before yesterday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914411 Title: Fix broken efifb on graphics device without driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914411] Re: Fix broken efifb on graphics device without driver
https://lore.kernel.org/linux- fbdev/20210129084327.986630-1-kai.heng.f...@canonical.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914411 Title: Fix broken efifb on graphics device without driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914411] Re: Fix broken efifb on graphics device without driver
SRU: https://lists.ubuntu.com/archives/kernel- team/2021-February/117003.html Currently NAK-ed for F/G for it's not yet in linux-next, but oem-5.10/U is open for further decision. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914411 Title: Fix broken efifb on graphics device without driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915870] Re: gnome session not starting (segfault in r300_dri.so)
** Summary changed: - gnome session not starting (segfault with r300_dri.so) + gnome session not starting (segfault in r300_dri.so) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome session not starting (segfault in r300_dri.so) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723130] Re: totem crashed with SIGSEGV in wl_proxy_add_listener() from wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from eglSwapBuffers() from _cogl_winsys_onscreen_swap_buff
No crashes reported after 18.04 so consider it fixed. ** Changed in: wayland (Ubuntu) Status: Confirmed => Fix Released ** Changed in: totem (Ubuntu) Status: Confirmed => Fix Released ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723130 Title: totem crashed with SIGSEGV in wl_proxy_add_listener() from wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from eglSwapBuffers() from _cogl_winsys_onscreen_swap_buffers_with_damage() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1723130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821281] Re: xenial-updates package wayland 1.12.0 fails to build when backported to trusty
I think it would be safe to say we don't care about Wayland support on Ubuntu 14.04. And the packages haven't been updated since 2018, which supports that. ** Tags added: trusty ** Changed in: wayland (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821281 Title: xenial-updates package wayland 1.12.0 fails to build when backported to trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726497] Re: nautilus crashed with SIGABRT in wl_abort() from wl_proxy_marshal_array_constructor_versioned()
No crashes reported after 19.04 so consider it fixed. ** Changed in: wayland (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726497 Title: nautilus crashed with SIGABRT in wl_abort() from wl_proxy_marshal_array_constructor_versioned() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1726497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
@Patricio, updated in the beginning of the bug description :)
** Description changed:
TL;DR
To bring up QCA6390, aka. AX500s, on Ubuntu 20.04 Focal, please first
update your system BIOS to the latest version available.
And then you will need both kernel (either oem-5.6, or oem-5.10, or
generic-5.11) and firmware with ath11k support:
[kernel]
1. oem-5.6 >= 5.6.0-1039.43
- $ sudo apt-get install linux-oem-20.04
+ $ sudo apt-get install linux-oem-20.04
- linux-oem-20.04 meta package may upgrade to v5.10 soon, but it will
+ linux-oem-20.04 meta package may upgrade to v5.10 soon, but it will
still support ath11k.
2. oem-5.10 >= 5.10.0-1010.11 (recommended)
- $ sudo apt-get install linux-oem-20.04b
+ $ sudo apt-get install linux-oem-20.04b
- This meta package may cease to exist after 5.10 oem kernel transition.
+ This meta package may cease to exist after 5.10 oem kernel transition.
Use linux-oem-20.04 then.
3. linux-generic-5.11
- $ sudo apt-add-repository ppa:canonical-kernel-team/bootstrap
- $ sudo sed -e 's,focal,devel,' -i
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-focal.list
- $ sudo mv
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-focal.list
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-devel.list
- $ sudo apt-get update
- $ sudo apt-get install $(apt-cache search linux-modules-extra-5.11 | awk
'{print $1}')
+ # Enable ppa:canonical-kernel-team/bootstrap for Hirsute:
+ $ sudo apt-add-repository ppa:canonical-kernel-team/bootstrap
+ $ sudo sed -e 's,focal,devel,' -i
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-focal.list
+ $ sudo mv
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-focal.list
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-devel.list
+
+ $ sudo apt-get update
+ $ sudo apt-get install $(apt-cache search linux-modules-extra-5.11 | awk
'{print $1}')
+
+ # Then rename the list to prevent unexpected upgrades:
+ $ sudo mv
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-devel.list
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-devel.list_
+ $ sudo apt update
[firmware]
Version 1.187.7 or newer is needed. So just do:
- $ sudo apt-get install linux-firmware
+ $ sudo apt-get install linux-firmware
Then reboot and check if wireless is now working. If doesn't, please
file a new bug instead.
== previous SRU justification header ==
[SRU Justification: oem-5.6]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k and all
its prerequisite drivers.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
Tag ath11k-qca6390-bringup-202011301608 from ath tree
(https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks
first stable milestone on the platform/device under development since
v5.6-rc1. Most of the commits under this tag, ~350 commits, have been
in vanilla kernel v5.10-rc4 except those starting from commit
065c9528cc50 ("ath11k: add 64bit check before reading msi high addr").
While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling
in these components are also pulled.
Besides, tx encapsulation
https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/
and a couple more inclusive of 6 GHz capability, BSS Color were also
pulled to satisfy API changes in mac80211/cfg80211.
[Test Case]
1. Install firmwares & boot from patched kernel,
2. ath11k should be now up and running. Check with
`sudo dmesg | grep ath11k`
While this is going to bring massive changes to the kernel, as well as
shared wireless stack that is not only used by ath11k but also many
others, prebuilt kernel/firmware packages were deployed on platforms
with and without ath11k for regression tests, and so far the results are
positive.
[Where problems could occur]
ath11k and its relying parts have never been enabled in oem-5.6, so
changes to them should have little effect on most platforms. For
platforms equip QCA6390, this will be the first time they're probed and
enabled, and as the driver is still under polishing, there can be
regressions, performance lost, power consumption increase at this
moment.
Changes to wireless stack could also be an issue as this introduces
interface changes to the API, so maybe DKMS packages in the wild will be
affected.
== SRU for U/OEM-5.10 ==
[SRU Justification: U/OEM-5.10]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k driver.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
[Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
** Description changed:
+ TL;DR
+
+ To bring up QCA6390, aka. AX500s, on Ubuntu 20.04 Focal, please first
+ update your system BIOS to the latest version available.
+
+ And then you will need both kernel (either oem-5.6, or oem-5.10, or
+ generic-5.11) and firmware with ath11k support:
+
+ [kernel]
+
+ 1. oem-5.6 >= 5.6.0-1039.43
+
+ $ sudo apt-get install linux-oem-20.04
+
+ linux-oem-20.04 meta package may upgrade to v5.10 soon, but it will
+ still support ath11k.
+
+ 2. oem-5.10 >= 5.10.0-1010.11 (recommended)
+
+ $ sudo apt-get install linux-oem-20.04b
+
+ This meta package may cease to exist after 5.10 oem kernel transition.
+ Use linux-oem-20.04 then.
+
+ 3. linux-generic-5.11
+
+ $ sudo apt-add-repository ppa:canonical-kernel-team/bootstrap
+ $ sudo sed -e 's,focal,devel,' -i
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-focal.list
+ $ sudo mv
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-focal.list
/etc/apt/sources.list.d/ppa-canonical-kernel-team-ubuntu-bootstrap-devel.list
+ $ sudo apt-get update
+ $ sudo apt-get install $(apt-cache search linux-modules-extra-5.11 | awk
'{print $1}')
+
+ [firmware]
+
+ Version 1.187.7 or newer is needed. So just do:
+
+ $ sudo apt-get install linux-firmware
+
+ Then reboot and check if wireless is now working. If doesn't, please
+ file a new bug instead.
+
+ == previous SRU justification header ==
+
[SRU Justification: oem-5.6]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k and all
its prerequisite drivers.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
- Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
+ Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
Tag ath11k-qca6390-bringup-202011301608 from ath tree
(https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks
first stable milestone on the platform/device under development since
v5.6-rc1. Most of the commits under this tag, ~350 commits, have been
in vanilla kernel v5.10-rc4 except those starting from commit
065c9528cc50 ("ath11k: add 64bit check before reading msi high addr").
While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling
in these components are also pulled.
Besides, tx encapsulation
https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/
and a couple more inclusive of 6 GHz capability, BSS Color were also
pulled to satisfy API changes in mac80211/cfg80211.
[Test Case]
1. Install firmwares & boot from patched kernel,
2. ath11k should be now up and running. Check with
-`sudo dmesg | grep ath11k`
+ `sudo dmesg | grep ath11k`
While this is going to bring massive changes to the kernel, as well as
shared wireless stack that is not only used by ath11k but also many
others, prebuilt kernel/firmware packages were deployed on platforms
with and without ath11k for regression tests, and so far the results are
positive.
[Where problems could occur]
ath11k and its relying parts have never been enabled in oem-5.6, so
changes to them should have little effect on most platforms. For
platforms equip QCA6390, this will be the first time they're probed and
enabled, and as the driver is still under polishing, there can be
regressions, performance lost, power consumption increase at this
moment.
Changes to wireless stack could also be an issue as this introduces
interface changes to the API, so maybe DKMS packages in the wild will be
affected.
== SRU for U/OEM-5.10 ==
[SRU Justification: U/OEM-5.10]
[Impact]
Qualcomm QCA6390 series not recognized due to the lack of ath11k driver.
$ lspci
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
[Fix]
25 additional fixes in ath tree
(https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag
ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms,
and firmware updates from mainline are required.
[Test Case]
1. Install firmwares & boot from patched kernel,
2. ath11k should be now up and running. Check with
`sudo dmesg | grep ath11k`
[Where problems could occur]
There has been a lot patches landed in kernel since 5.7 devel cycle. The
last bits here has merge base with mainline at v5.10-rc4, and since then
only patches for ath11k itself has been committed.
== Original Bug Description ==
Qualcomm QCA6390 series not recognized due to the lack of ath11k driver.
:55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
[Bug 1916684] [NEW] [FFe] OVS fix duplicate mac address failures on bonds
Public bug reported: [Description] OVS environments which make use of bonds run into duplicate mac errors preventing cloud-init from setting up networking on those machines.[1] This FFe is to minimally fix LP: 1912844 to unblock OVS deployments. [Rationale] This changeset (under development) needs to land in hirsute before cloud-init can SRU into prior Ubuntu releases. So we would like to submit this FFe to get it into Hirsute so it can ultimately be SRUd back into earlier releases. [Timeline] Current development is in flight and expected within 1-2 weeks. We expect minimally one branch, but cloud-init recently uploaded tip of master as version 21.1 to Hirsute (on 2/23/21) so there would not be much delta/risk if a full new upstream snapshot release were performed. [Risks] Low risk as the code related to this changeset should only be triggered on OVS platforms where bonds are present because the code path is slower. [1] OVS: duplicate MAC bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844 ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916684 Title: [FFe] OVS fix duplicate mac address failures on bonds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1916684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
So sad, Asus doesn't care about linux users, that's the reality ... Our only hope is a community developed driver for this feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904249] Re: nvidia: module license 'NVIDIA' taints kernel
@Peter, please file a new bug instead as this one is about thermal control and has expired. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904249 Title: nvidia: module license 'NVIDIA' taints kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909950] Re: named: TCP connections sometimes never close due to race in socket teardown
Performing verification for Bind9 on Focal.
I first installed 9.16.1-0ubuntu2.6 from -updates to ensure that the
issue is still present.
I checked that I could look up ubuntu.com through the local caching
resolver. From there I started a second VM, and checked I could look up
addresses through the first VM. I then added the 30% packet loss rule
with tc. From there I opened up 11 tabs in gnome-terminal and hit the
first first VM with:
$ for run in {1..1}; do dig +tcp @192.168.122.21 ubuntu.com & done
https://paste.ubuntu.com/p/sF9SXkWpZK/
We can see that the "TCP high-water" mark kept rising until it reached
150, when I then killed the thundering herd from the second VM. I then
did a DNS lookup, and found that named was not listening to TCP, and the
lookup timed out.
This confirms that 9.16.1-0ubuntu2.6 from -updates is affected.
I then enabled -proposed, and installed bind9 9.16.1-0ubuntu2.7 and
rebooted.
>From there, I can checked I could look up ubuntu.com through the local
caching resolver, and again started the second VM. The second VM could
also look up addresses through the first VM. I again added a 30% packet
loss with tc. I then opened up 11 tabs of gnome-terminal and hit the
first vm with the dig for loop of doom.
Except this time, once I reached the TCP high water mark and killed the
second VM, the number of TCP connections fell back down to 1, and did
not get stuck at a higher number. I did a TCP DNS lookup for ubuntu.com
on the server, and the request was successful and did not time out.
named is listening to TCP connections as it is suppose to.
https://paste.ubuntu.com/p/SzJMzz6xbh/
bind9 9.16.1-0ubuntu2.7 fixes the problem. Happy to mark as verified.
I will also write back in a few days time with feedback from a user, who
is testing this fixed package in production.
** Tags removed: verification-needed 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/1909950
Title:
named: TCP connections sometimes never close due to race in socket
teardown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
Thanks for the tip, I've disabled secure boot, restarted into 5.11 but still no HDMI connection. $ uname -r 5.11.0-051100drmtip20210223-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916623] Re: xog not installed
'xog' is not a valid package that can be installed, but that looks like a typo... 'xorg' is also not an important package that provides any binaries. So this doesn't appear to be a valid bug report. Can you explain exactly what kind of problem you are experiencing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916623 Title: xog not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1916623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916623] Re: xog not installed
'xog' is not a valid package that can be installed, but that looks like a typo... 'xorg' is also not a valid package that can be installed because it's just the name of a source package. So this doesn't appear to be a valid bug report. Can you explain exactly what kind of problem you are experiencing? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916623 Title: xog not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1916623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915870] Re: gnome session not starting (segfault with r300_dri.so)
** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Changed in: mesa (Ubuntu) Status: Confirmed => Triaged ** Tags added: fixed-in-21 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome session not starting (segfault with r300_dri.so) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916594] Re: Xorg freeze
Thanks for the bug report. Next time the freeze happens, please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Please also check for crashes which might have caused the apparent freeze using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1916594 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1916594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy
Thanks. That log shows gnome-shell (for the login screen?) died because Xorg went away: Feb 23 07:30:15 gnome-shell[3625]: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Also there is evidence of a common freezing problem that happens with the Nvidia driver: Feb 23 08:31:40 gnome-shell[8333]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Feb 23 08:31:40 gnome-shell[8333]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Next please follow the instructions in comments #5 and #11 and attach the resulting text files here in full. Please also check for crashes from the system using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1516 https://gitlab.gnome.org/GNOME/mutter/-/issues/1516 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy
Also, that "common freezing problem that happens with the Nvidia driver" is being tracked upstream in https://gitlab.gnome.org/GNOME/mutter/-/issues/1516 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909352] Re: [nvidia] (1) video hangs or (2) screen goes blank and case fan turns on
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then 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. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-460 (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/1909352 Title: [nvidia] (1) video hangs or (2) screen goes blank and case fan turns on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1909352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
I'm getting a "kernel taint" message with Nvidia-460 ; not sure if it is related to this bug, reference https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904249/comments/3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818260] Re: forget cluster node failed during cluster-relation-changed hook
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818260 Title: forget cluster node failed during cluster-relation-changed hook To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1818260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904249] Re: nvidia: module license 'NVIDIA' taints kernel
I have NVIDIA Driver Version: 460.32.03 installed, and have had display and font issues $ dmesg | grep nvidia [0.805138] nvidia: loading out-of-tree module taints kernel. [0.805151] nvidia: module license 'NVIDIA' taints kernel. [0.836165] nvidia: module verification failed: signature and/or required key missing - tainting kernel [0.848083] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 [0.966956] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 460.32.03 Sun Dec 27 18:51:11 UTC 2020 [0.968185] [drm] [nvidia-drm] [GPU ID 0x0800] Loading driver [0.968187] [drm] Initialized nvidia-drm 0.0.0 20160202 for :08:00.0 on minor 1 [ 12.317149] nvidia-uvm: Loaded the UVM driver, major device number 235. [ 42.863316] caller os_map_kernel_space.part.0+0x77/0xa0 [nvidia] mapping multiple BARs [ 7858.114245] nvidia :08:00.0: Enabling HDA controller -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904249 Title: nvidia: module license 'NVIDIA' taints kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911036] Re: GDK/GTK app crash when performing drag operation
Thanks for those crash reports. Unfortunately they don't have any stack traces for some reason... Since you seem to be pretty technical, the next steps I suggest are: 1. Install the debug symbols for gtk and apps like thunar. 2. Attach 'gdb' to thunar or any affected app. 3. Reproduce the crash. 4. Get a 'bt' backtrace from gdb and paste it here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash when performing drag operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1911036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
This bug does not appear to be related to Xfce, yet. If it does happen in Xubuntu then please add a new task at the top of the page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812892] Re: Use high ram memory by the gnome-shell-extension-gsconnect
** Tags added: gnome-shell-leak -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812892 Title: Use high ram memory by the gnome-shell-extension-gsconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-gsconnect/+bug/1812892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885085] Re: Suspend is not deep
Same problem and same solution in my ASUS Laptop X513EQ. Ubuntu 20.04 Kernel: 5.4 - 5.6 - 5.8 - 5.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885085 Title: Suspend is not deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1885085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error
I experienced exactly the same problem on Ubuntu 20.04. I solved this way: 1. First I stopped cups-browsed: systemctl stop cups-browsed 2. Then I manually added my printer (an HP OfficeJet 6950) clicking on the "Add.." button in the Preferences, and manually selected the name from the database, so it won't use any driverless print protocol. Did a test print and it worked. 3. I removed the automatically created printer 4. Restarted cups-browsed: systemctl start cups-browsed After that, the printer worked as expected and wasn't automatically added any more, even after a system reboot. The only minor issue is that for some reason I can't rename the printer from the Preferences, but since it's my only I can live with it for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855595 Title: CUPS fails to print to autodetected printers because of cups-browsed error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897965] Re: PulseAudio doesn't work when pipewire is installed (ie. KDE)
Yeah the changelog sounds like it's talking about this issue being fixed: pipewire (0.3.19-3) unstable; urgency=medium * Team upload * Don't enable audio-related plugins by default. Using pipewire for audio is considered experimental for Debian 11, and in particular the with-pulseaudio flag file will result in PulseAudio and Pipewire fighting over Bluetooth devices. - If you're experimenting with pipewire-pulse, please see /usr/share/doc/pipewire-audio-client-libraries/README.Debian for details of how to re-enable these. but looking deeper at the debdiff I don't understand how it was done. Let's assume this is indeed fixed in hirsute... ** Changed in: pipewire (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/1897965 Title: PulseAudio doesn't work when pipewire is installed (ie. KDE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1897965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
reply #47 Hello, it is because the secure boot. would you please disable secure boot in your bios? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916570] Re: BlueZ 5.56 release
Yeah. I have merged with Debian in the past but not recently. Unfortunately this one needs to be released quickly for feature freeze tomorrow. So I have no plans to merge with Debian till at least next cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916570 Title: BlueZ 5.56 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1916570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914670] Re: No HDMI detection
I'm having trouble booting with the 5.11 kernel. After manually selecting to boot into 5.11 from the advanced boot options page, I'm getting 'invalid signature' error. From the link you've provided, I've downloaded the following packages: 1) amd64/linux- headers-5.11.0-051100drmtip20210223-generic_5.11.0-051100drmtip20210223.202102230209_amd64.deb 2) amd64/linux- headers-5.11.0-051100drmtip20210223_5.11.0-051100drmtip20210223.202102230209_all.deb 3) amd64/linux-image- unsigned-5.11.0-051100drmtip20210223-generic_5.11.0-051100drmtip20210223.202102230209_amd64.deb 4) amd64/linux- modules-5.11.0-051100drmtip20210223-generic_5.11.0-051100drmtip20210223.202102230209_amd64.deb Then proceeded to put them under the same folder and ran "$ sudo dpkg -i *.deb" The problems I'm seeing now is the default boot version at the very top of the grub boot loader is still 5.8, and unable to boot when manually selecting 5.11 (which is located much lower with a weird name like 5.11.0-051100drmtip20210223 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914670 Title: No HDMI detection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907713] Re: aufs support is deprecated and should be handled on upgrade
Although there's no reason for the deb's preinst to be checking /var/snap/docker/common/var-lib-docker/aufs surely? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907713 Title: aufs support is deprecated and should be handled on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916550] Re: simple-scan chooses scanned image size improperly
Unable to comply - here is what I get when I run soimple-scan from the
command line - it never fires the scanner properly and all I get is
errors:
$ simple-scan -d
[+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=1139752
[+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0.02s] DEBUG: _g_io_module_get_default: Found default implementation gvfs
(GDaemonVfs) for ‘gio-vfs’
[+0.05s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.08s] DEBUG: app-window.vala:1906: Loading state from
/home/admar/.cache/simple-scan/state
[+0.08s] DEBUG: app-window.vala:1885: Restoring window to 2506x1175 pixels
[+0.15s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
[+0.15s] DEBUG: scanner.vala:1545: SANE version 1.0.29
[+0.15s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
[+0.15s] DEBUG: scanner.vala:828: Processing request
[+0.50s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+7.16s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+7.52s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+7.57s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7.57s] DEBUG: scanner.vala:353: Device:
name="hpaio:/usb/OfficeJet_4650_series?serial=TH7B64F03Z0662"
vendor="Hewlett-Packard" model="OfficeJet_4650_series" type="all-in-one"
[+7.57s] DEBUG: scanner.vala:353: Device: name="escl:https://192.168.1.107:443;
vendor="ESCL" model="HP OfficeJet 4650 series [A67ED8] SSL" type="flatbed
scanner"
[+7.57s] DEBUG: scanner.vala:353: Device: name="escl:http://127.0.0.1:6;
vendor="ESCL" model="OfficeJet 4650 series [TH7B64F03Z0662]" type="flatbed
scanner"
[+7.57s] DEBUG: scanner.vala:353: Device: name="escl:http://192.168.1.107:8080;
vendor="ESCL" model="HP OfficeJet 4650 series [A67ED8]" type="flatbed scanner"
[+7.88s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+9.02s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+11.78s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+14.75s] DEBUG: simple-scan.vala:1536: Requesting scan at 300 dpi from device
'hpaio:/usb/OfficeJet_4650_series?serial=TH7B64F03Z0662'
[+14.75s] DEBUG: scanner.vala:1674: Scanner.scan
("hpaio:/usb/OfficeJet_4650_series?serial=TH7B64F03Z0662", dpi=300,
scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, paper_height=0,
brightness=0, contrast=13, delay=3000ms)
[+14.75s] DEBUG: scanner.vala:828: Processing request
(simple-scan:1139752): Gtk-WARNING **: 17:22:33.786: Calling
org.xfce.Session.Manager.Inhibit failed:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method
“Inhibit”
(simple-scan:1139752): Gtk-WARNING **: 17:22:33.787: Calling
org.xfce.Session.Manager.IsInhibited failed:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method
“IsInhibited”
[+14.76s] DEBUG: scanner.vala:889: sane_open
("hpaio:/usb/OfficeJet_4650_series?serial=TH7B64F03Z0662") ->
SANE_STATUS_IO_ERROR
[+14.76s] WARNING: scanner.vala:893: Unable to open device: Error during device
I/O
[+15.30s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+20.42s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+35.67s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+40.79s] DEBUG: autosave-manager.vala:265: Waiting to autosave...
[+40.89s] DEBUG: autosave-manager.vala:287: Autosaving book information
[+41.09s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+43.99s] DEBUG: simple-scan.vala:1536: Requesting scan at 300 dpi from device
'hpaio:/usb/OfficeJet_4650_series?serial=TH7B64F03Z0662'
[+43.99s] DEBUG: scanner.vala:1674: Scanner.scan
("hpaio:/usb/OfficeJet_4650_series?serial=TH7B64F03Z0662", dpi=300,
scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, paper_height=0,
brightness=0, contrast=13, delay=3000ms)
[+43.99s] DEBUG: scanner.vala:828: Processing request
[+44.00s] DEBUG: scanner.vala:889: sane_open
("hpaio:/usb/OfficeJet_4650_series?serial=TH7B64F03Z0662") ->
SANE_STATUS_IO_ERROR
[+44.00s] WARNING: scanner.vala:893: Unable to open device: Error during device
I/O
[+44.57s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+48.95s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+53.25s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+91.31s] DEBUG: app-window.vala:1981: Saving state to
/home/admar/.cache/simple-scan/state
[+92.43s] DEBUG: autosave-manager.vala:201: Deleting autosave records
[+92.43s] DEBUG: scanner.vala:1702: Stopping scan thread
[+92.43s] DEBUG: scanner.vala:828:
[Bug 1812892] Re: Use high ram memory by the gnome-shell-extension-gsconnect
When I enable GSConnect version 28 (as reported by GSConnect > About) in Tweaks > Extensions > GSConnect, after a while my Ubuntu 18.04 system becomes unresponsive, with the disk activity light solidly on. With it disabled, the system never becomes unresponsive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812892 Title: Use high ram memory by the gnome-shell-extension-gsconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-gsconnect/+bug/1812892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904399] Re: [OVN] Inconsistent "flooding to unregistered" IGMP configuration
This is now blocking the acceptance of the 17.1.0 SRU from unapproved for both focal and groovy. Could someone please do the SRU testing for this package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904399 Title: [OVN] Inconsistent "flooding to unregistered" IGMP configuration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1904399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532264] Please test proposed package
Hello Christopher, or anyone else affected, Accepted fprintd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fprintd/1.90.9-1~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532264 Title: fprintd allows unauthorized root access To manage notifications about this bug go to: https://bugs.launchpad.net/fprintd/+bug/1532264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532264] Re: fprintd allows unauthorized root access
Hello Christopher, or anyone else affected, Accepted fprintd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fprintd/1.90.9-1~ubuntu20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: fprintd (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: fprintd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532264 Title: fprintd allows unauthorized root access To manage notifications about this bug go to: https://bugs.launchpad.net/fprintd/+bug/1532264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789177] Re: RabbitMQ fails to synchronize exchanges under high load
ah sorry corey you already uploaded it to bionic as well. thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789177 Title: RabbitMQ fails to synchronize exchanges under high load To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888495] Please test proposed package
Hello Marco, or anyone else affected, Accepted fprintd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fprintd/1.90.9-1~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888495 Title: fprintd-verify fails with an USB UPEK reader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888495] Re: fprintd-verify fails with an USB UPEK reader
Hello Marco, or anyone else affected, Accepted fprintd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fprintd/1.90.9-1~ubuntu20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: fprintd (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: fprintd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888495 Title: fprintd-verify fails with an USB UPEK reader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908119] Please test proposed package
Hello Marco, or anyone else affected, Accepted fprintd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fprintd/1.90.9-1~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908119 Title: Update and SRU 1.90.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1908119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908119] Re: Update and SRU 1.90.9
Hello Marco, or anyone else affected, Accepted fprintd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fprintd/1.90.9-1~ubuntu20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: fprintd (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: fprintd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908119 Title: Update and SRU 1.90.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1908119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789177] Re: RabbitMQ fails to synchronize exchanges under high load
I've confirmed that only 1st patch is ok with below steps 1. deploy queens 2. patch nuetron node's oslo.messaging (1st patch only) except nova-compute node's oslo.messaging 3. trying to create instance and delete And I keep restarting cinder-scheduler while I blocked one rabbitmq- server with iptables -A INPUT -p tcp --dport 5672 -j DROP I was able to see no exchange error for cinder eventually. I'm going to prepare 1st and 3rd commit debdiff for this patch today. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789177 Title: RabbitMQ fails to synchronize exchanges under high load To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916670] [NEW] sddm-greeter crashes with segfault (Bad RIP value) before login shows up on Lubuntu 20.04.2 LTS
Public bug reported: After installing the latest Lubuntu 20.04.2 LTS on my laptop, i wasnt able to log on into that system anymore. The system runs into a mouse cursor only visible black screen with no greeter to log in. Switching to console and login into terminal is just fine and all works as expected on terminal level. Restarting the sddm (service sddm restart) didnt work. Reinstalling/reconfiguring (purging orphaned conf file before) sddm and lubuntu-desktop didnt help. After some investigation on the log files, i found out that the sddm-greeter process crashes for reasons unknown with a bad instruction pointer value. More info below. dmesg: [71.601020] sddm-greeter[1084]: segfault at 0 ip sp 7ffe946a7ed8 error 14 in sddm-greeter[55bc43ab+17000] [71.601030] Code: Bad RIP value. System Arch: amd64 lsb_release -a: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal uname -r: 5.4.0-66-generic apt-cache show sddm: Package: sddm Architecture: amd64 Version: 0.18.1-1ubuntu2 Priority: optional Section: universe/kde Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian/Kubuntu Qt/KDE Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1916 Provides: x-display-manager Depends: adduser, qml-module-qtquick2, xauth, x11-common, xserver-xorg | xserver, debconf (>= 0.5) | debconf-2.0, libc6 (>= 2.14), libgcc-s1 (>= 3.0), libpam0g (>= 0.99.7.1), libqt5core5a (>= 5.12.2), libqt5dbus5 (>= 5.6.0~), libqt5gui5 (>= 5.6.0~beta) | libqt5gui5-gles (>= 5.6.0~beta), libqt5network5 (>= 5.6.0~), libqt5qml5 (>= 5.0.2), libqt5quick5 (>= 5.0.2) | libqt5quick5-gles (>= 5.0.2), libstdc++6 (>= 5.2), libsystemd0, libxcb-xkb1, libxcb1 Recommends: haveged, libpam-systemd, sddm-theme-debian-maui | sddm-theme Suggests: libpam-kwallet5, qtvirtualkeyboard-plugin Filename: pool/universe/s/sddm/sddm_0.18.1-1ubuntu2_amd64.deb Size: 631728 MD5sum: 7926cf1daefe2f0d730dd592342d15c1 SHA1: 4d37b7b88160a7fd2235c7fd296cdbeb1d042a91 SHA256: e894e61102080f66e397eb462d418a7c490ac91e0499d3becbf0a8011bd0a429 Homepage: https://github.com/sddm/sddm Description-en: modern display manager for X11 SDDM is a modern display manager for X11 aiming to be fast, simple and beautiful. It uses modern technologies like QtQuick to create smooth, animated user interfaces. Description-md5: 60d2ea934d7c99b8460547a3b6ef2196 Task: kubuntu-desktop, kubuntu-full, lubuntu-desktop ** Affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916670 Title: sddm-greeter crashes with segfault (Bad RIP value) before login shows up on Lubuntu 20.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1916670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916669] Re: autopkgtests flaky for hirsute across various architectures
** Merge proposal linked: https://code.launchpad.net/~alexmurray/britney/+git/hints-ubuntu/+merge/398573 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916669 Title: autopkgtests flaky for hirsute across various architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1916669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907713] Re: aufs support is deprecated and should be handled on upgrade
The attachment "lp1907713.debdiff" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907713 Title: aufs support is deprecated and should be handled on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916669] [NEW] autopkgtests flaky for hirsute across various architectures
Public bug reported: Currently the lxc 1:4.0.4-1:4.0.4-0ubuntu3 and 1:4.0.6-0ubuntu1 autopkgtests for hirsute are quite flaky across most architectures: amd64 - https://autopkgtest.ubuntu.com/packages/l/lxc/hirsute/amd64 --- only 3 out of the last 8 runs were successful even after multiple manual retries for the same trigger package. arm64 - https://autopkgtest.ubuntu.com/packages/l/lxc/hirsute/arm64 --- only 3 out of the last 10 runs were successful even after multiple manual retries for the same trigger package. s390x - https://autopkgtest.ubuntu.com/packages/l/lxc/hirsute/s390x --- only 1 out of the last 12 runs were successful even after multiple manual retries for the same trigger package. ppc64el - https://autopkgtest.ubuntu.com/packages/l/lxc/hirsute/ppc64el --- this seems to be running better more recently but was failing previously for the same trigger packages against the same lxc package As such I feel it makes sense to mark both of these versions as force- reset-test so that lxc failures do not block other packages migrating. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916669 Title: autopkgtests flaky for hirsute across various architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1916669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916356] Re: The installer failed to create partition on disk with EFI (not BIOS)
Launchpad has imported 3 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=432941. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-02-14T16:18:20+00:00 Andrius Štikonas wrote: Support dosfstools 4.2 See https://github.com/calamares/calamares/issues/1637 Reply at: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1916356/comments/0 On 2021-02-19T17:52:53+00:00 Andrius Štikonas wrote: Git commit 36dfae351ffac48134e2697b4fc1024e7557e319 by Andrius Štikonas. Committed on 19/02/2021 at 17:51. Pushed by stikonas into branch 'master'. Add initial support for dosfstools 4.2. Empty labels are not allowed anymore. One can reset them with -r flag but that is not supported in older dosfstools. So for now we just manually set label to NO_LABEL. M +3-1src/fs/fat12.cpp https://invent.kde.org/system/kpmcore/commit/36dfae351ffac48134e2697b4fc1024e7557e319 Reply at: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1916356/comments/1 On 2021-02-19T17:53:55+00:00 Andrius Štikonas wrote: Git commit 00de13088995ae96cf660911196fceda096e5b19 by Andrius Štikonas. Committed on 19/02/2021 at 17:53. Pushed by stikonas into branch 'release/20.12'. Add initial support for dosfstools 4.2. Empty labels are not allowed anymore. One can reset them with -r flag but that is not supported in older dosfstools. So for now we just manually set label to NO_LABEL. M +3-1src/fs/fat12.cpp https://invent.kde.org/system/kpmcore/commit/00de13088995ae96cf660911196fceda096e5b19 Reply at: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1916356/comments/2 ** Changed in: kpmcore Status: Unknown => Fix Released ** Changed in: kpmcore Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916356 Title: The installer failed to create partition on disk with EFI (not BIOS) To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1916356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916668] Re: package bacula-director-pgsql 9.4.2-2ubuntu5 failed to install/upgrade: installed bacula-director-pgsql package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916668 Title: package bacula-director-pgsql 9.4.2-2ubuntu5 failed to install/upgrade: installed bacula-director-pgsql package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1916668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916668] [NEW] package bacula-director-pgsql 9.4.2-2ubuntu5 failed to install/upgrade: installed bacula-director-pgsql package post-installation script subprocess returned error exit status 1
Public bug reported: just trying to update package and got this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bacula-director-pgsql 9.4.2-2ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: postfix:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Feb 21 00:33:48 2021 ErrorMessage: installed bacula-director-pgsql package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-18 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bacula Title: package bacula-director-pgsql 9.4.2-2ubuntu5 failed to install/upgrade: installed bacula-director-pgsql package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bacula (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916668 Title: package bacula-director-pgsql 9.4.2-2ubuntu5 failed to install/upgrade: installed bacula-director-pgsql package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1916668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
