[Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg
*** This bug is a duplicate of bug 2038313 *** https://bugs.launchpad.net/bugs/2038313 Not sure if related, but having similar graphical failures for nautilus, gnome-control-center, etc. Using nvidia-driver-535. Had a similar upgrade case to https://bugs.launchpad.net/ubuntu/+bug/2061257/comments/6 where it failed initially and I recovered it. Similar output of `libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped)` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Same issue upgrading from 22.04 to 24.04, confirmed the fix of `sudo apt install systemd-resolved` fixes the issue. Had a crash partway through the upgrade where I was left with the UI showing "something went wrong", which was partially fixed by dropping into a terminal and commadning `sudo dpkg --configure -a`, but it was left in this state afterwards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058500] [NEW] invalid metadata error w/wheel system package
Public bug reported:
This seems to be cosmetic; arguably a pip problem but it would likely be
much easier to fix in wheel packaging. sid has a 0.43, maybe upgrade
and it goes away?
#14 9.722 WARNING: Skipping
/usr/lib/python3.12/dist-packages/wheel-0.42.0.dist-info due to invalid
metadata entry 'name'
For example:
$ pip install --break-system-packages django
WARNING: Skipping /usr/lib/python3.12/dist-packages/wheel-0.42.0.dist-info due
to invalid metadata entry 'name'
Collecting django
Downloading Django-5.0.3-py3-none-any.whl.metadata (4.2 kB)
Collecting asgiref<4,>=3.7.0 (from django)
Downloading asgiref-3.8.0-py3-none-any.whl.metadata (9.3 kB)
Collecting sqlparse>=0.3.1 (from django)
Downloading sqlparse-0.4.4-py3-none-any.whl.metadata (4.0 kB)
Downloading Django-5.0.3-py3-none-any.whl (8.2 MB)
8.2/8.2 MB 12.3 MB/s eta 0:00:00
Downloading asgiref-3.8.0-py3-none-any.whl (23 kB)
Downloading sqlparse-0.4.4-py3-none-any.whl (41 kB)
41.2/41.2 kB 737.4 kB/s eta 0:00:00
WARNING: Skipping /usr/lib/python3.12/dist-packages/wheel-0.42.0.dist-info due
to invalid metadata entry 'name'
Installing collected packages: sqlparse, asgiref, django
Successfully installed asgiref-3.8.0 django-5.0.3 sqlparse-0.4.4
WARNING: Running pip as the 'root' user can result in broken permissions and
conflicting behaviour with the system package manager. It is recommended to use
a virtual environment instead: https://pip.pypa.io/warnings/venv
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)"
$ apt show python3-wheel
Package: python3-wheel
Version: 0.42.0-1
** Affects: wheel (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/2058500
Title:
invalid metadata error w/wheel system package
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wheel/+bug/2058500/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
Follow-up from my previous comment. The build appears to fail if I try to run it twice without running "clean" in between. In other words, to successfully build, I ran: fakeroot debian/rules clean fakeroot debian/rules binary-headers binary-generic binary-perarch The drawback is it rebuilds everything (which is about 45 minutes on my machine). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047683 Title: Kernel build fails on debian/build/tools- perarch/tools/bpf/bpftool/vmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
I experienced a similar issue building 6.5.0-25 on Ubuntu 22.04. I followed the steps in the "Build Your Own Kernel" post: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel Specifically, the error occurs after I ran the build step with the parameters: fakeroot debian/rules binary-headers binary-generic binary-perarch I tried the LLVM and CC tricks mentioned in the previous post, but it did not help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047683 Title: Kernel build fails on debian/build/tools- perarch/tools/bpf/bpftool/vmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968790] Re: Webview for SAML does not allow Duo to use a Yubikey
I don't think this is an openconnect issue? Or are you handling network manager issues there too? I see the Ubuntu patch was merged upstream since this was opened? "External browser" would be nice, but IT says we can't turn it on, needs some upgrade, and CISCO says not to use it: The saml external-browser command is for migration purposes for those upgrading to AnyConnect 4.6 or later. Because of security limitations, use this solution only as part of a temporary migration while upgrading AnyConnect software. The command itself will be depreciated in the future. Since the latest Anyconnect client on Windows got the integrated browser upgraded to Edge and now supports all security key flows I'm not optimistic our deployment will ever enable it. So what we really want to see is something like network-manager- openconnect that can support webauthn, with CTAP2 support, but that seems alarmingly hard :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968790 Title: Webview for SAML does not allow Duo to use a Yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1968790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968790] Re: Webview for SAML does not allow Duo to use a Yubikey
Upon more research it seems there is alot more wrong here than the misleading message from Duo. GTK Webkit completely lacks support for webauthn, so it is pointless to think about anything at the network-manager-openconnect level. This means this will not support security tokens for VPN login. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968790 Title: Webview for SAML does not allow Duo to use a Yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1968790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897171] Re: package is misconfigured or missing version files, resulting in ocamlfind not knowing its version
This continues to be a problem in impish, jammy, and kinetic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897171 Title: package is misconfigured or missing version files, resulting in ocamlfind not knowing its version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lablgtk3/+bug/1897171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964437] Re: Jammy liblablgtk3-ocaml, liblablgtksourceview3-ocaml, liblablgtk3-ocaml-dev, and liblablgtksourceview3-ocaml-dev 3.1.2-1 report the wrong version
See also https://bugs.launchpad.net/ubuntu/+source/lablgtk3/+bug/1897171 (I didn't realize I had already reported this two years ago...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964437 Title: Jammy liblablgtk3-ocaml, liblablgtksourceview3-ocaml, liblablgtk3-ocaml-dev, and liblablgtksourceview3-ocaml-dev 3.1.2-1 report the wrong version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lablgtk3/+bug/1964437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897171] Re: package is misconfigured or missing version files, resulting in ocamlfind not knowing its version
See also https://bugs.launchpad.net/ubuntu/+source/lablgtk3/+bug/1964437 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897171 Title: package is misconfigured or missing version files, resulting in ocamlfind not knowing its version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lablgtk3/+bug/1897171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973669] [NEW] 10_linuxzfs fails if a non-root filesystem has a mountpoint of /
Public bug reported:
For ~4 years, this server ran Ubuntu-18.04 with the OS on mirrored SSDs
and all persistent data in a zpool on separate disks. Last week I
upgraded it. Installation of Ubuntu-22.04 ZFS-root on a new SSD ran
flawlessly. But after importing the persistent data pool, update-grub
(specifically 10_linux_zfs) found the valid kernels but wouldn't create
grub entries for them so /boot/grub/grub.cfg only contained memtest86.
10_linux_zfs's section of grub-mkconfig output is below.
The problem turned out to be a FreeBSD backup I'd zfs-send/rec'd to the
Ubuntu system 2 years ago. At the time, I added a prefix ("zmule") to
all of the FreeBSD filesystems' mountpoints and turned off "canmount".
Somehow I missed the *actual* root filesystem so it was still set to
mount on '/' with "canmount" enabled - though Ubuntu22.04 wouldn't mount
it on top of /, so I never noticed it. However, that's what was
confusing /etc/grub.d/10_linux_zfs even though 18.04 was fine with it.
Once I changed FreeBSD's root mountpoint to not '/', update-grub ran as
expected.
I know this is a strange, unusual situation that shouldn't happen, but a
missing /etc/os-release file in one root(ish) filesystem shouldn't block
it from creating entries for valid ones. If you'd like me to break it
again and run 10_linux_zfs with 'set -x' or similar, I'll be happy to do
that. (I'm a Linux SRE professionally so breaking stuff is all in a
days work.)
One more note: the bug submission wouldn't let me use "grub-common" as
the package, so I changed that to "grub2" even though, as you can see
below, that's not what's installed.
===
More detail:
$ lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04
$ apt-cache policy grub-common
grub-common:
Installed: 2.06-2ubuntu7
Candidate: 2.06-2ubuntu7
Version table:
*** 2.06-2ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy grub2
grub2:
Installed: (none)
Candidate: 2.06-2ubuntu7
Version table:
2.06-2ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
-
### BEGIN /etc/grub.d/10_linux_zfs ###
Found linux image: vmlinuz-5.15.0-27-generic in rpool/ROOT/ubuntu_lva06t
Found initrd image: initrd.img-5.15.0-27-generic in rpool/ROOT/ubuntu_lva06t
Found linux image: vmlinuz-5.15.0-25-generic in rpool/ROOT/ubuntu_lva06t
Found initrd image: initrd.img-5.15.0-25-generic in rpool/ROOT/ubuntu_lva06t
/etc/grub.d/10_linux_zfs: 404: .: cannot open
/tmp/zfsmnt.Z7nWCz/etc/os-release: No such file
-
$ zfs get mountpoint persist/backup/mule-zfs/ROOT/default
NAMEPROPERTYVALUE SOURCE
persist/backup/mule-zfs/ROOT/defaultmountpoint / local
-
# oops! This fixed it:
$ sudo zfs set mountpoint=zmule persist/backup/mule-zfs/ROOT/default
$ zfs get mountpoint persist/backup/mule-zfs/ROOT/default
NAMEPROPERTYVALUE SOURCE
persist/backup/mule-zfs/ROOT/defaultmountpoint /zmule local
** Affects: grub2 (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/1973669
Title:
10_linuxzfs fails if a non-root filesystem has a mountpoint of /
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1973669/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970923] Re: [SRU][F/J] Update firmware of MT7922
@ Juerg, Thanks for the help to comment the new firmware for mt7922. Can you help to advise when will be the new linux-firmware with this fix landing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970791] [NEW] Starting ejabberd with systemctl "hangs" on Ubuntu 22.04 with apparmor profile
Public bug reported: When starting or restarting ejabberd with systemctl on Ubuntu 22.04, the systemctl command hangs until there is a tiemout. Ejabberd seems to start just fine but fails to notify systemd that it has started. While ejabberd is running man log messages such as the folloing go to /var/log/syslog: pr 28 15:13:23 devjam kernel: [23209.114137] audit: type=1400 audit(1651173203.101:2332): apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ejabberdctl" name="run/systemd/notify" pid=29578 comm="5_scheduler" requested_mask="w" denied_mask="w" fsuid=115 ouid=0 Disabling the apparmor profile for usr.sbin.ejabberdctl seems to resolve this. ** Affects: ejabberd (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/1970791 Title: Starting ejabberd with systemctl "hangs" on Ubuntu 22.04 with apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1970791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1968467] Re: CSD scripts do not work on jammy
That does, work, note that the leading and trailing _ are garbage, file should be: root@c5c1367d7a8e:/# cat /tmp/openssl.conf openssl_conf = openssl_init [openssl_init] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] Options = UnsafeLegacyRenegotiation root@c5c1367d7a8e:/# OPENSSL_CONF=/tmp/openssl.conf curl -k -v https://xxx/CACHE/sdesktop/hostscan/linux_x64/manifest [..] < HTTP/1.1 200 OK < Content-Type: < Content-Length: 813 < Cache-Control: max-age=6000 Thanks, Jason On Fri, Apr 22, 2022 at 12:10 AM Dan Lenski <1968...@bugs.launchpad.net> wrote: > @jgunthorpe, what if you do something like this, where you create an > OPENSSL_CONF that explicitly (re)enables unsafe legacy negotiation? > Instead of using /dev/null. > > ``` > $ cat > /tmp/openssl.conf < _openssl_conf = openssl_init > [openssl_init] > ssl_conf = ssl_sect > [ssl_sect] > system_default = system_default_sect > [system_default_sect] > Options = UnsafeLegacyRenegotiation_ > EOF > > $ OPENSSL_CONF=/tmp/openssl.conf curl > ``` > > That comes from https://github.com/dlenski/gp-saml-gui/issues/42 > > ** Bug watch added: github.com/dlenski/gp-saml-gui/issues #42 >https://github.com/dlenski/gp-saml-gui/issues/42 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1968467 > > Title: > CSD scripts do not work on jammy > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968790] [NEW] Webview for SAML does not allow Duo to use a Yubikey
Public bug reported: Thanks a lot for working on the new SAML support for openconnect, I just succeeded to make it work with our cisco anyconnect setup - it is going to make a lot of people happy here. Is there any thing I can do to help get the upstream parts merged - eg confirm it works etc? For this bug - one thing I hope is simple to resolve is that the webview that is spawned causes Duo MFA to complain it cannot use a Yubikey U2F token because popups are blocked - can popups be unblocked? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openconnect-gnome 1.2.6-4 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 20:44:56 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-openconnect UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openconnect (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968790 Title: Webview for SAML does not allow Duo to use a Yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1968790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1968467] Re: CSD scripts do not work on jammy
On Mon, Apr 11, 2022 at 6:00 PM Dan Lenski <1968...@bugs.launchpad.net> wrote: > > My feeling is that curl should set the SSL option when -k is used. > openconnect itself sets this option already, it was fixed in commit > c8dcf10 > > If you replace the cURL invocation in the CSD/Trojan script with… > > ``` > OPENSSL_CONF=/dev/null curl > ``` > > … does this make it work? (For some hints about how/why it should work, > No, it didn't change, I tested with: # OPENSSL_CONF=/dev/null curl -k -v https://x.x.x.x/ * ALPN, offering h2 * ALPN, offering http/1.1 * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (OUT), TLS header, Unknown (21): * TLSv1.2 (OUT), TLS alert, handshake failure (552): * error:0A000152:SSL routines::unsafe legacy renegotiation disabled * Closing connection 0 curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation disabled Inside ubuntu:22.04 as a docker container just to test curl. Thanks, Jason -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968467] [NEW] CSD scripts do not work on jammy
Public bug reported: The CSD scripts all use curl to communicate to the ASA server and in Jammy curl has been linked with openssl 3. openssl 3 switched off SSL_OP_LEGACY_SERVER_CONNECT by default, and CISCO never implemented RFC5746 in ASA so the curl commands in the CSD script just fail to connect (and the scripts blindly ignore these errors making it hard to debug) When run manually curl reports back: * ALPN, offering h2 * ALPN, offering http/1.1 * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (OUT), TLS header, Unknown (21): * TLSv1.2 (OUT), TLS alert, handshake failure (552): * error:0A000152:SSL routines::unsafe legacy renegotiation disabled * Closing connection 0 curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation disabled My feeling is that curl should set the SSL option when -k is used. openconnect itself sets this option already, it was fixed in commit c8dcf10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openconnect 8.20-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 12:19:57 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openconnect UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openconnect (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897171] Re: package is misconfigured or missing version files, resulting in ocamlfind not knowing its version
Note that this bug makes it impossible to compile CoqIDE on jammy. Is there any eta on getting this fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897171 Title: package is misconfigured or missing version files, resulting in ocamlfind not knowing its version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lablgtk3/+bug/1897171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04
Well funny you should say that... When I installed 22.04 on my new Dell laptop with 16G RAM, Jammy still only allocated 976MB of swap. I think you have a problem there too. So after reporting this issue and continually having OOM crashes, I created a 20G swapfile - and ever since this problem has disappeared... Maybe running with such a starved swapspace triggers systemd-oom to do weird things? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967004] Re: Manual partitioning requires "esp" flag on /boot/efi partition, but that flag isn't offered as an option, and the "boot" flag mysterious makes the warning go away
Okay, upstream, this is a known and fixed bug: https://github.com/calamares/calamares/issues/1192 ** Bug watch added: Calamares Issues #1192 https://github.com/calamares/calamares/issues/1192 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967004 Title: Manual partitioning requires "esp" flag on /boot/efi partition, but that flag isn't offered as an option, and the "boot" flag mysterious makes the warning go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1967004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967004] [NEW] Manual partitioning requires "esp" flag on /boot/efi partition, but that flag isn't offered as an option, and the "boot" flag mysterious makes the warning go away
Public bug reported: Installing Lubuntu 20.04. Opted for manual partitioning of my disks. Created a /boot/efi partition with no flags. After hitting NEXT from the partioning screen, I see a "What is your name?" screen, but a dialog box pops up with an warning. Title: EFI system partition flag not set Contents: An EFI System partition is necessary to start Lubuntu A partion was configured with mount point /boot/efi but its esp flag was not set. To set the flag, go back and edit the partition. You can continue without setting the flag but your system may fail to start. >>> But going back, "esp" isn't one of the available flags offered on the "Create a Partition" dialog. I tried setting the "boot" flag for /boot/efi instead, and I was able to pass through to the next screen without seeing that warning. If I remove the "boot" flag for /boot/efi, the warning is displayed again. I'm guessing that the "esp" flag requirement is outdated, and it should be changed to a "boot" flag requirement. Probably the wording of this dialog box needs to change. As it stands, it is very confusing. ** Affects: calamares-settings-ubuntu (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/1967004 Title: Manual partitioning requires "esp" flag on /boot/efi partition, but that flag isn't offered as an option, and the "boot" flag mysterious makes the warning go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1967004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04
Oh well, that latest systemd-oom didn't help. Chrome just crashed again - while I wasn't even using the computer. Here are all the syslogs at the time it crashed - nothing but the OOM Mar 28 19:30:56 ubuntu systemd-oomd[1121]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-google\x2dchrome-5640.scope due to memory used (15992975360) / total (16153948160) and swap used (921436160) / total (1023406080) being more than 90.00% Mar 28 19:30:56 ubuntu systemd[5083]: app-gnome-google\x2dchrome-5640.scope: systemd-oomd killed 311 process(es) in this unit. Mar 28 19:30:56 ubuntu systemd[5083]: app-gnome-google\x2dchrome-5640.scope: Consumed 7h 10min 56.132s CPU time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966603] [NEW] gnome shell add-on in FF broke with forced move to snap version
Public bug reported: Looks like the FF add-on that allows you to review/alter gnome-shell extensions no longer works now that firefox is a snap. It was working when I initially installed Ubuntu-22.04 two weeks ago (I chose native apt of FF over snap then), but last week there was the announcement-and- forced-move over to a snap - I would guess that's when it broke. I just now removed the add-on from within FF, restarted FF, added it back in - and it still doesn't work. I have a bunch of FF add-ons (like uBlock Origin) and I think they are working - so this seems fairly specific to "Gnome Shell Extension" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 07:39:22 2022 InstallationDate: Installed on 2022-03-13 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966603 Title: gnome shell add-on in FF broke with forced move to snap version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966602] [NEW] Screen not locked after inactivity
Public bug reported: I did a fresh install of Ubuntu-22.04 two weeks ago. I don't think the automatic lock on idle feature has worked the entire time (and I've been patching all the time when available). If I manually lock the screen it works - but if I don't, I can go to bed and the next day it's still unlocked. syslog doesn't show any obvious gnome-screensaver error, so I wonder if this is actually a Wayland issue - ie it isn't telling gnome- screensaver about inactivity triggers? I dunno - just guessing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver 3.6.1-13ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 07:06:47 2022 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 900 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2022-03-13 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-screensaver Symptom: security Title: Screen not locked after inactivity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966602 Title: Screen not locked after inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1966602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04
FYI About 6 hours ago I saw a new release of systemd-oom was released (249.11-0ubuntu2). I've upgraded the entire system and rebooted, so I'll report back if there's any change. I was getting these random OOM about every couple of days, so within a week should know if that changed anything -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966381] [NEW] applications crash that never crashed under Ubuntu-20.04
Public bug reported: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto-choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966037] [NEW] some applications hang for up to 30sec due to /run/systemd/resolve/io.systemd.Resolve
Public bug reported: I just installed Ubuntu-22.04 last week and have noticed lots of command line apps seem to hang for 10-30sec before working. Eventually that got annoying enough that I looked into it. Anyway, apps like "telnet" (yep, I'm that old) and oddly enough sudo showed this issue strongly. In the end I ran them with strace and could see the pause occurred when /run/systemd/resolve/io.systemd.Resolve was called. So systemd-resolve was involved. Then I cranked up "tcpdump -n -i any port 53" and re-ran the commands. What I found was systemd-resolver was throwing DNS lookups for my hostname at all the DNS servers I had configured (default on wifi plus corporate always-on VPN link). Now the thing is our corporate VPN has SIXTEEN domains in the search domain field... So as systemd-resolver was doing one "A" plus one "" lookups for each "hostname.search-domain" - well there's the hang. In fact 30sec is quite a good response time ;-) To fix it I simply added my raw (ie non-dot) hostname to /etc/hosts - completely blocked this self-hostname lookup that must be going on. Now there are no DNS lookups at all for my hostname in this situation. All is good. But it does make me wonder if perhaps Ubuntu shouldn't always put the hostname into /etc/hosts? Even pointing at 127.0.0.99 (for example) might be enough (I haven't actually tested that - I'm pointing it at my static VPN IP) Anyway, this is a corner case for sure - but it might shave some delays off a bunch of folks. This also might seem cosmetic, but I would guess any application that calls gethostbyname or equivalent on itself is triggering this. PS: I had Ubuntu-20.04 before this and didn't have the problem. But looking at a backup I can see I also had my hostname in the /etc/hosts file - so this might have affected 20.04 too but I "accidentally" fixed it early on without realizing it ** Affects: systemd (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/1966037 Title: some applications hang for up to 30sec due to /run/systemd/resolve/io.systemd.Resolve To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965214] Re: keep getting asked to set a Primary Password?
Sigh. Please close ticket. After hitting Send I went and looked at Preferences again and NOW I see there's a Security section where you can turn off the Primary Password feature. Sorry for wasting your time. :-/ Jason ** Changed in: remmina (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965214 Title: keep getting asked to set a Primary Password? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965214] [NEW] keep getting asked to set a Primary Password?
Public bug reported: Under Ubuntu-22.04beta I am continually getting prompted to set what I assume is a master password for remmina cred changes. The issue is that I have it configured to save to gnome-keyring. And if I bring up that gnome-keyring I can see the remmina creds I've saved in there - so all is good on that front. ie the gnome-keyring and whatever this "primary password" thing is are doing the same thing and only one should win - the latter should be disabled. There doesn't seem to be any way to disable it - I am just hitting cancel and it keeps popping up later. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: remmina 1.4.24+dfsg-2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 16:06:00 2022 InstallationDate: Installed on 2022-03-13 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: remmina (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965214 Title: keep getting asked to set a Primary Password? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965088] [NEW] mouse selects creates solid white blocks in remmina?
Public bug reported: I've used remmina for years and normally don't fiddle with defaults much. I've moved from Ubuntu-20.04 to 22.04beta and I've noticed that my Linux SSH sessions now have weird mouse behaviour. If I use the mouse to "Select" content, instead of the traditional "transparent" format occurring, I see a solid white area. eg if I selected a screenful of content in gnome-terminal, the default purple background with white text becomes white background with black text. But in remmina, the black background with white text becomes white background with white text - ie it's all white. Just to reiterate, if I do the same action in gnome-terminal or firefox/etc it is "normal" - this seems to be remmina-specific Any ideas how to fix this? Thanks Jason ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: remmina 1.4.24+dfsg-2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 19:30:50 2022 InstallationDate: Installed on 2022-03-13 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965088 Title: mouse selects creates solid white blocks in remmina? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964437] Re: Jammy liblablgtk3-ocaml, liblablgtksourceview3-ocaml, liblablgtk3-ocaml-dev, and liblablgtksourceview3-ocaml-dev 3.1.2-1 report the wrong version
There is a NixOS patch for this at https://github.com/NixOS/nixpkgs/pull/155871/files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964437 Title: Jammy liblablgtk3-ocaml, liblablgtksourceview3-ocaml, liblablgtk3-ocaml-dev, and liblablgtksourceview3-ocaml-dev 3.1.2-1 report the wrong version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lablgtk3/+bug/1964437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964437] [NEW] Jammy liblablgtk3-ocaml, liblablgtksourceview3-ocaml, liblablgtk3-ocaml-dev, and liblablgtksourceview3-ocaml-dev 3.1.2-1 report the wrong version
Public bug reported: On March 4, [my Coq launchpad package succeeded with](https://launchpadlibrarian.net/589055712/buildlog_ubuntu-jammy-amd64.coq_8.master~git~202203042103+23110-0~daily375-aedb9bc5f3~ubuntu22.04.1_BUILDING.txt.gz) ``` LablGtk3 and LablGtkSourceView3 found (3.1.1), with native threads: => native CoqIDE will be built. ``` However, on March 8, [the same build script failed due to](https://launchpadlibrarian.net/589689507/buildlog_ubuntu-jammy-amd64.coq_8.master~git~202203082103+23112-0~daily375-a0df849836~ubuntu22.04.1_BUILDING.txt.gz) ``` LablGtk3 and LablGtkSourceView3 found ([unspecified]), but too old (required >= 3.1.0, found [unspecified]): => no CoqIDE will be built. ``` The difference is that liblablgtk3-ocaml, liblablgtksourceview3-ocaml, liblablgtk3-ocaml-dev, and liblablgtksourceview3-ocaml-dev got upgraded from 3.1.1+official-1build2 to 3.1.2-1. Apparently `ocamlfind query -format %v lablgtk3` now gives "[unspecified]" instead of a real version number. ** Affects: lablgtk3 (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/1964437 Title: Jammy liblablgtk3-ocaml, liblablgtksourceview3-ocaml, liblablgtk3-ocaml-dev, and liblablgtksourceview3-ocaml-dev 3.1.2-1 report the wrong version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lablgtk3/+bug/1964437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950317] Re: [MIR] Wireguard
apw's reasoning is correct. I do wonder, though, if at some point we can start looking into sunsetting the dkms package entirely and the wireguard-linux-compat backport with it. It's been mainlined for a good deal of time now. We'd have to do some analysis of which kernels people run Ubuntu with are so old that they don't have it, and I'm not sure how exactly to perform that analysis. But maybe it's something to consider down the road. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950317 Title: [MIR] Wireguard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960036] Re: [SRU] Doesn't regain quorum when tracked process restarts with PID > 32767
version tested: 2.0.19-2ubuntu0.2 tested keepalived ability to regain quorum after the tracked process (with high numbers pid) restarts. Based on my testing the version tested fixes the reported issue. I do not know if it introduces new bugs. I only tested to see if it fixes the reported issue. Note: after downgrading back to 2.0.19-2ubuntu0.1 the issue re appears. testing output ``` pre patch pp01 stop haproxy service Feb 16 11:30:26 pp01 systemd[1]: Stopping HAProxy Load Balancer... Feb 16 11:30:26 pp01 systemd[1]: haproxy.service: Succeeded. Feb 16 11:30:26 pp01 systemd[1]: Stopped HAProxy Load Balancer. Feb 16 11:30:27 pp01 Keepalived_vrrp[18854]: Quorum lost for tracked process track_haproxy Feb 16 11:30:27 pp01 Keepalived_vrrp[18854]: (LB_VIP) Changing effective priority from 111 to 101 Feb 16 11:30:31 pp01 Keepalived_vrrp[18854]: (LB_VIP) Master received advert from 10.4.150.182 with higher priority 110, ours 101 Feb 16 11:30:31 pp01 Keepalived_vrrp[18854]: (LB_VIP) Entering BACKUP STATE Feb 16 11:30:54 pp01 systemd[1]: Starting HAProxy Load Balancer... Feb 16 11:30:54 pp01 systemd[1]: Started HAProxy Load Balancer. start haproxy service -- nothing restart haproxy service eb 16 11:32:15 pp01 systemd[1]: Stopping Keepalive Daemon (LVS and VRRP)... Feb 16 11:32:16 pp01 Keepalived_vrrp[18854]: Released DBus Feb 16 11:32:16 pp01 Keepalived_vrrp[18854]: Stopped Feb 16 11:32:16 pp01 Keepalived[18853]: Stopped Keepalived v2.0.19 (10/19,2019) Feb 16 11:32:16 pp01 systemd[1]: keepalived.service: Succeeded. Feb 16 11:32:16 pp01 systemd[1]: Stopped Keepalive Daemon (LVS and VRRP). Feb 16 11:32:16 pp01 systemd[1]: Started Keepalive Daemon (LVS and VRRP). Feb 16 11:32:16 pp01 Keepalived[511543]: Starting Keepalived v2.0.19 (10/19,2019) Feb 16 11:32:16 pp01 Keepalived[511543]: Running on Linux 5.11.0-1028-aws #31~20.04.1-Ubuntu SMP Fri Jan 14 14:37:50 UTC 2022 (built for Linux 5.4.151) Feb 16 11:32:16 pp01 Keepalived[511543]: Command line: '/usr/sbin/keepalived' '--dont-fork' Feb 16 11:32:16 pp01 Keepalived[511543]: Opening file '/etc/keepalived/keepalived.conf'. Feb 16 11:32:16 pp01 Keepalived[511543]: Starting VRRP child process, pid=511544 Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Registering Kernel netlink reflector Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Registering Kernel netlink command channel Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Opening file '/etc/keepalived/keepalived.conf'. Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: (LB_VIP) Changing effective priority from 101 to 111 Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Registering gratuitous ARP shared channel Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: (LB_VIP) Entering BACKUP STATE (init) Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Acquired DBus bus org.keepalived.Vrrp1 Feb 16 11:32:16 pp01 Keepalived_vrrp[511544]: Acquired the name org.keepalived.Vrrp1 on the session bus Feb 16 11:32:17 pp01 Keepalived_vrrp[511544]: (LB_VIP) received lower priority (110) advert from 10.4.150.182 - discarding Feb 16 11:32:20 pp01 Keepalived_vrrp[511544]: message repeated 3 times: [ (LB_VIP) received lower priority (110) advert from 10.4.150.182 - discarding] Feb 16 11:32:20 pp01 Keepalived_vrrp[511544]: (LB_VIP) Entering MASTER STATE pp02 stop haproxy service Feb 16 11:30:28 pp02 Keepalived_vrrp[399]: (LB_VIP) received lower priority (101) advert from 10.4.150.181 - discarding Feb 16 11:30:30 pp02 Keepalived_vrrp[399]: message repeated 2 times: [ (LB_VIP) received lower priority (101) advert from 10.4.150.181 - discarding] Feb 16 11:30:31 pp02 Keepalived_vrrp[399]: (LB_VIP) Entering MASTER STATE start haproxy service -- nothing restart haproxy service Feb 16 11:32:20 pp02 Keepalived_vrrp[399]: (LB_VIP) Master received advert from 10.4.150.181 with higher priority 111, ours 110 Feb 16 11:32:20 pp02 Keepalived_vrrp[399]: (LB_VIP) Entering BACKUP STATE - post patch pp01 stop haproxy service eb 16 11:35:03 pp01 systemd[1]: Stopping HAProxy Load Balancer... Feb 16 11:35:03 pp01 systemd[1]: haproxy.service: Succeeded. Feb 16 11:35:03 pp01 systemd[1]: Stopped HAProxy Load Balancer. Feb 16 11:35:04 pp01 Keepalived_vrrp[511912]: Quorum lost for tracked process track_haproxy Feb 16 11:35:04 pp01 Keepalived_vrrp[511912]: (LB_VIP) Changing effective priority from 111 to 101 Feb 16 11:35:07 pp01 Keepalived_vrrp[511912]: (LB_VIP) Master received advert from 10.4.150.182 with higher priority 110, ours 101 Feb 16 11:35:07 pp01 Keepalived_vrrp[511912]: (LB_VIP) Entering BACKUP STATE start haproxy service Feb 16 11:35:45 pp01 systemd[1]: Starting HAProxy Load Balancer... Feb 16 11:35:45 pp01 Keepalived_vrrp[511912]: Quorum gained for tracked process track_haproxy Feb 16 11:35:45 pp01 Keepalived_vrrp[511912]: (LB_VIP) Changing effective priority from 101 to 111 Feb 16 11:35:46 pp01 systemd[1]: Started HAProxy Load Balancer. Feb 16 11:35:46 pp01 Keepalived_vrrp[511912]: (LB_VIP) received lower priority (110) advert
[Bug 1960036] Re: Doesnt regain quorum when tracked process restarts
Here are both of the keepalived configs, Both after about as basic as
they get. I am not sure how to force the high pid's. If you need more
information from me, just let me know.
primary keepalived config (update ips to match your environment)
```
# Global Settings for notifications
global_defs {
enable_script_security
script_user keepalived_script
enable_dbus
}
vrrp_track_process track_haproxy {
process haproxy
weight 10
delay 1
}
# Configuration for Virtual Interface
vrrp_instance LB_VIP {
interface ens5
state MASTER
priority 101
virtual_router_id 51
authentication {
auth_type PASS
auth_pass somepassword # Password for accessing vrrpd. Same on all
devices, only up to 8 chars
}
unicast_src_ip 10.1.1.3 # Private IP address of primary
unicast_peer {
10.1.1.4 # Private IP address of the secondary haproxy
}
# The virtual ip address shared between the two loadbalancers
virtual_ipaddress {
10.1.1.2
}
# Use the Defined Script to Check whether to initiate a fail over
#track_script {
#chk_haproxy
#}
track_process {
track_haproxy
}
}
```
backup keepalived config
```
# Global Settings for notifications
global_defs {
enable_script_security
script_user keepalived_script
enable_dbus
}
vrrp_track_process track_haproxy {
process haproxy
weight 10
delay 1
}
# Configuration for Virtual Interface
vrrp_instance LB_VIP {
interface ens5
state BACKUP
priority 100
virtual_router_id 51
authentication {
auth_type PASS
auth_pass somepass # Password for accessing vrrpd. Same on all
devices, only up to 8 chars
}
unicast_src_ip 10.1.1.4 # Private IP address of primary
unicast_peer {
10.1.1.3 # Private IP address of the secondary haproxy
}
# The virtual ip address shared between the two loadbalancers
virtual_ipaddress {
10.1.1.2
}
track_process {
track_haproxy
}
}
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960036
Title:
Doesnt regain quorum when tracked process restarts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1960036/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960036] [NEW] Doesnt regain quorum when tracked process restarts
Public bug reported: Keepalived doesn't regain quorum when using tracked process due to a bug in high numbered pids The upstream has already fixed in a patch release 2.0.20 https://serverfault.com/questions/993432/keepalived-doesnt-gain-quorum- when-tracked-process-comes-up Could we please get the 2.0.20 released to 20.04 ** Affects: keepalived (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/1960036 Title: Doesnt regain quorum when tracked process restarts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1960036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957847] [NEW] display output detection problem
Public bug reported: dell precision M6800 KERNEL 5.4.0-94 attempts to activate vga while not plugged in, deactivates, cyclic screen blackout, shape/size ** Affects: linux (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/1957847 Title: display output detection problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956398] Re: [Ruby Pass] Ubuntu with AST2600 mini DP Display doesn't work (OS Mode)
@jeff The current ASPEED AST2600 driver fails to install on Ubuntu 21.10. With Ubuntu 20.04 LTS, the display is blank until the driver is installed. Can you try this with the latest daily image for 22.04 (as the target is 22.04)?: [Jan/11] We still face same issue. Installed the image (Ubuntu 22.04 LTS (Jammy Jellyfish) Daily Build: https://cdimage.ubuntu.com/daily-live/current/) Screen can’t display during installation & enter to OS. These 2 methods (install driver to 20.04 LTS and patch) are short term method to continue our EVT testing without problem. Can we have Canonical team build an 20.04 OS image to include AST 2600 Driver? Long term, we'd expect that AST2600 driver will be part of 22.04 LTS image. Thanks -Jason -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956398 Title: [Ruby Pass] Ubuntu with AST2600 mini DP Display doesn't work (OS Mode) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1956398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956988] [NEW] KDE connect simply crashed
Public bug reported: === Info === PID: 3076 (kdeconnectd) UID: 1000 (jason) GID: 1000 (jason) Signal: 11 (SEGV) Timestamp: Mon 2022-01-10 07:17:16 CST (4h 16min ago) Command Line: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd Executable: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service Unit: user@1000.service User Unit: dbus.service Slice: user-1000.slice Owner UID: 1000 (jason) Boot ID: 27f1b62d5464432798c4b00c36823c51 Machine ID: c4f2d44acf3c4564bf5a66409c42613f Hostname: jason-Precision-M6800 Storage: /var/lib/systemd/coredump/core.kdeconnectd.1000.27f1b62d5464432798c4b00c36823c51.3076.1641820636.lz4 Message: Process 3076 (kdeconnectd) of user 1000 dumped core. Stack trace of thread 3076: #0 0x7f3d0cd5f4d4 _ZNK6Device4nameEv (libkdeconnectcore.so.1 + 0x5c4d4) #1 0x7f3d0cd3ce86 _ZN18CompositeUploadJob10slotResultEP4KJob (libkdeconnectcore.so.1 + 0x39e86) #2 0x7f3d0b89c328 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5 + 0x2b2328) #3 0x7f3d0bc18c60 _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF5CoreAddons.so.5 + 0x49c60) #4 0x7f3d0bc1976b _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x4a76b) #5 0x7f3d0b89c328 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5 + 0x2b2328) #6 0x7f3d0b7b2b4d _ZN9QIODevice5closeEv (libQt5Core.so.5 + 0x1c8b4d) #7 0x7f3d0b7a9d03 _ZN11QFileDevice5closeEv (libQt5Core.so.5 + 0x1bfd03) #8 0x7f3d0cd3d478 _ZN9UploadJob16uploadNextPacketEv (libkdeconnectcore.so.1 + 0x3a478) #9 0x7f3d0b89c328 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5 + 0x2b2328) #10 0x7f3d0b06ed46 _ZN10QSslSocket21encryptedBytesWrittenEx (libQt5Network.so.5 + 0x11ed46) #11 0x7f3d0b070aed n/a (libQt5Network.so.5 + 0x120aed) #12 0x7f3d0b079d3d n/a (libQt5Network.so.5 + 0x129d3d) #13 0x7f3d0b89c1d0 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5 + 0x2b21d0) #14 0x7f3d0b7af5b6 _ZN9QIODevice12bytesWrittenEx (libQt5Core.so.5 + 0x1c55b6) #15 0x7f3d0b03cb41 n/a (libQt5Network.so.5 + 0xecb41) #16 0x7f3d0b03d648 n/a (libQt5Network.so.5 + 0xed648) #17 0x7f3d0b04ee6f n/a (libQt5Network.so.5 + 0xfee6f) #18 0x7f3d0c3d1a66 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16aa66) #19 0x7f3d0c3db0f0 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1740f0) #20 0x7f3d0b87080a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28680a) #21 0x7f3d0b8c9095 n/a (libQt5Core.so.5 + 0x2df095) #22 0x7f3d0a03d17d g_main_context_dispatch (libglib-2.0.so.0 + 0x5217d) #23 0x7f3d0a03d400 n/a (libglib-2.0.so.0 + 0x52400) #24 0x7f3d0a03d4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #25 0x7f3d0b8c8435 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2de435) #26 0x7f3d0b86f3ab _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2853ab) #27 0x7f3d0b877116 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x28d116) #28 0x5605c8b61e78 n/a (kdeconnectd + 0x3e78) #29 0x7f3d0b23b0b3 __libc_start_main (libc.so.6 + 0x270b3) #30 0x5605c8b6214e _start (kdeconnectd + 0x414e) Stack trace of thread 3188: #0 0x7f3d0b329aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f3d0a03d36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f3d0a03d4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f3d0b8c8435 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2de435) #4 0x7f3d0b86f3ab _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2853ab) #5 0x7f3d0b6a7785 _ZN7QThread4execEv (libQt5Core.so.5 + 0xbd785) #6 0x7f3d0b6a89d2 n/a (libQt5Core.so.5 + 0xbe9d2) #7 0x7f3d0a8fe609 start_thread (libpthread.so.0 + 0x9609) #8
[Bug 1923007] Re: graphite-carbon 1.1.4-2 crashes
The workaround above (#2) seems to work in my environment. Thanks for posting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923007 Title: graphite-carbon 1.1.4-2 crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite-carbon/+bug/1923007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948723] Re: /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma? raise Exceptions.LayoutFileError("Unrecognized
I believe that the patch below will fix the issue:
--- /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py.orig
2021-12-20 22:34:49.184112471 -0500
+++ /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py 2021-12-20
22:33:33.374611161 -0500
@@ -445,7 +445,7 @@
except KeyError as ex:
(strerror) = ex
raise Exceptions.LayoutFileError("Unrecognized modifier %s in"
\
-"definition of %s" (strerror, full_id))
+"definition of %s".format(strerror, full_id))
value = attributes.get("action")
if value:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948723
Title:
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447:
SyntaxWarning: 'str' object is not callable; perhaps you missed a
comma? raise Exceptions.LayoutFileError("Unrecognized modifier %s
in" \
To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1948723/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953337] Re: Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378)
Thank you very much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953337 Title: Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1953337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953337] [NEW] Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378)
*** This bug is a security vulnerability *** Public security bug reported: Dear community, Qualys reports a finding on our Ubuntu 18.04 and Ubuntu 20.04 instances because of CVE-2021-42378. I can see that there is already a fix for Ubuntu 22.04. When will the fix be released for the LTS versions 18.04 and 20.04? I can see the finding is monitored at https://ubuntu.com/security/CVE-2021-42378, but the CVSS3 scoring is 7.2, so I think the rating "high" would be better. Or is there any reason why "low" is ok? Thanks in advance. Best regards. ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-42378 ** Information type changed from Private Security to Public Security ** Information type changed from Public Security to Private Security ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953337 Title: Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1953337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950403] Re: Grub failed to install at end of Mate installation on Dell Optiplex 390 64bit Intelx86 corei5
Hey I'm sorry. I just saw a notification. My system is working. I cannot reproduce issue. I can reinstall with my new media? I created a new install media with newer release. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950403 Title: Grub failed to install at end of Mate installation on Dell Optiplex 390 64bit Intelx86 corei5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584483] Re: Kubuntu live cd Destop folder widget too small.
Kubuntu no longer uses a desktop folder widget, so this issue can’t happen. ** Changed in: 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/1584483 Title: Kubuntu live cd Destop folder widget too small. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1584483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950317] Re: [MIR] Wireguard
> I was pointed at the existing debian bug requesting to drop the wireguard-dkms package The place where we still want wireguard-dkms, though, is for when people are running Ubuntu on strange kernels that might not have it out of the box. These are, of course, becoming increasingly rare. Probably the thing to do here is just to drop that package at the same time Debian does, whenever Debian does. > Jason, this is the DEP8 test I wanted to add to src:wireguard before I saw that src:wireguard-linux-compat had one already: https://git.launchpad.net/~ahasenack/ubuntu/+source/wireguard/tree/debian/tests/wireguard- wgquick?h=jammy-wireguard-dep8 That looks fine to me, though I find the use of "right" and "left" a bit too IPsec for my tastes :-). One thing you could do is do all the keygen inline with the script. For example: key1="$(pp wg genkey)" key2="$(pp wg genkey)" pub1="$(pp wg pubkey <<<"$key1")" pub2="$(pp wg pubkey <<<"$key2")" If I recall correctly, the netns-mini test I made does this, though that uses a slightly different topology, avoiding veth. Your test also uses wg-quick, which is neat, so maybe combining everything into one would be a decent idea, depending on how motivated you are. There's also this monster set of tests in the kernel tree, if you're looking for trouble: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/wireguard/netns.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950317 Title: [MIR] Wireguard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950317] Re: [MIR] Wireguard
Glad to hear the result. Thanks for working through this and hearing me out on IRC as well. With regards to the TODO: > I suggest the server team to reach out to @unit193 as the MOTU who maintained Unit193 is really top-notch and knows the project well, is an active participant with upstream, and generally is pretty on top of things. I don't know whether MIRing this means some sort of hand off involved, but I'd say that to the extent you can keep him in the fold, it's some nice expertise to keep around. > - does NOT have a test suite that runs at build time, we should add at least > the trivial autopkgtest generating and checking keys, as suggested > - does NOT have a non-trivial test suite that runs as autopkgtest, we should > integrate more testing (LP: #1952102) as suggested by adding the new "vpn" > test and/or copying the non-trivial autopkgtest from wireguard-linux-compat Let me know if you guys need help scripting these up. Indeed taking the wireguard-linux-compat case is probably a good place to start. But if you want something more elaborate and need a hand, just poke me on IRC. > + wireguard-dkms: recommended by wireguard-tools, it's part of the same > source >package, but we probably want to drop that, as we have the WireGuard > modules >in the kernel. Or at least we'd want to change Recommends: wireguard-dkms > to >Suggests: wireguard-dkms (LP: #1873288) I'd suggest you sync up with @apw about this. He was involved in some of the earlier discussions about this. And @unit193 too. Details are a bit fuzzy to me, but I think there's something interesting happening with the `wireguard` metapackage pulling in `wireguard-tools` and a `wireguard-modules` virtual package. That `wireguard-modules` virtual package is then satisfied by wireguard-dkms, wireguard-linux-compat, and the various Canonical kernel packages. Or something like that. I don't see a need for this to change. But... > recommended by wireguard-tools, it's part of the same source package This part confused me. Many many eons ago, WireGuard was one repo, with src/* having dkms kernel sources and src/tools/* containing the tools package. For a long long time now, this has been split up. But I wonder if the wireguard-tools package still has something left over from the days when dkms was mixed with it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950317 Title: [MIR] Wireguard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf
I think he meant to post this on https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892798 Title: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950317] Re: [MIR] Wireguard
I agree that's pretty weird. And especially for wg(8), that's not just a configuration tool; that's the low level inspection tool. Netplan can configure IP addresses; are you going to move ip(8) out of main too? If ip(8) is in main, then wg(8) should be in main. Netplan doesn't replace the low level inspection tools. It's a high level thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950317 Title: [MIR] Wireguard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Confirmed that this is still an issue in focal. It is only an issue if I log onto a XFCE session and then log out, these two processes stay around: /usr/libexec/geoclue-2.0/demos/agent /usr/bin/python3 /usr/share/system-config-printer/applet.py When I remove the geoclue-2.0 from the system: sudo apt -y purge geoclue-2.0 --autoremove The issue no longer shows up. I don't see neither processes hanging around any more. I think those two are related to the two autostart programs: /etc/xdg/autostart/geoclue-demo-agent.desktop /etc/xdg/autostart/print-applet.desktop I think in terms of workaround, two options here: 1. remove geoclue - but the catch here is that if you autoremove, gnome dependencies may get removed, which could have unexpected outcome 2. remove autostart files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950403] [NEW] Grub failed to install at end of Mate installation on Dell Optiplex 390 64bit Intelx86 corei5
Public bug reported: I have a Dell Optiplex Desktop with win 10 After updating Win10 and attempting install of Ubuntu Mate Desktop, it failed at the very end with Grup installation error ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 Date: Tue Nov 9 20:31:48 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu-mate ** Attachment added: "partman" https://bugs.launchpad.net/bugs/1950403/+attachment/5539385/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950403 Title: Grub failed to install at end of Mate installation on Dell Optiplex 390 64bit Intelx86 corei5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940136] Re: HyperV images do not include package manifests
Tested and confirmed fix on Focal. Bionic and Hirsute forthcoming tomorrow. Sorry for the delay; I did not understand next steps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940136 Title: HyperV images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1940136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883335] Re: Changing volume from "Indicator Applet Complete" mutes alert sounds.
Just did a fresh install of Ubuntu MATE 20.04 LTS this week and I can confirm this is still a problem. I can go into Sound Settings - Sound Effects Tab and turn up the Alert Volume slider, I can hear the laert beep, but the volume is not changed no matter where the slider is set, and as soon as I close the Sound Settings window, the volume slider is reset to 0. In fact, no sound settings are being saved after a reboot, logout, or resume from suspend or hibernate. Every time I reboot, login, or resume from suspend, I have to manually go into sound settings and re-select the (HDMI 2) output of my video card as the source.. for some reason it keeps defaulting back to HDMI 1. I have the on-board sound disabled in the bios, and it no longer shows up in the OS as a source, only my video card shows up as an audio source. I am using a Nvidia GT 1030 card, running the latest tested proprietary driver (metapackage from nvidia-driver-470). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883335 Title: Changing volume from "Indicator Applet Complete" mutes alert sounds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1883335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445976] Re: Panel set to autohide may not always retract
I just did a fresh install of Ubuntu MATE 20.04LTS on a Dell Optiplex 390. I am still having this problem... at least 5 years after reporting it as a bug. Why is this still a bug 6 versions later? Why is it marked as "low priority"? When the task bar doesn't hide like it should, it covers up applications and prevents access to things like scroll bars and buttons... I'd have to say that's a pretty high priority since it interferes with the overall function and productivity of the OS & DE. When can we expect a real permanent fix for this ongoing lack of proper functionality? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445976 Title: Panel set to autohide may not always retract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1445976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
The amd64 version still isn't built after the build failure, how can we get that build restarted? Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943491] [NEW] GIMP Batch Process crashes after doing a batch format change
Public bug reported:
```
GNU Image Manipulation Program version 2.10.24
git-describe: GIMP_2_10_24
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
9.3.0-17ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
# Libraries #
using babl version 0.1.86 (compiled against version 0.1.86)
using GEGL version 0.4.30 (compiled against version 0.4.30)
using GLib version 2.64.6 (compiled against version 2.64.6)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.44.7 (compiled against version 1.44.7)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> GIMP-CRITICAL: _gimp_wire_read_int8: assertion 'count >= 0' failed
Stack trace:
```
# Stack traces obtained from PID 36692 - Thread 36692 #
[New LWP 36693]
[New LWP 36694]
[New LWP 36695]
[New LWP 36696]
[New LWP 36697]
[New LWP 36698]
[New LWP 36699]
[New LWP 36700]
[New LWP 36701]
[New LWP 36702]
[New LWP 36721]
[New LWP 36774]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffcf5b33ea0, fd=19) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f0320673340 (LWP 36692) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7ffcf5b33ea0, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f031ff27700 (LWP 36693) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f031f726700 (LWP 36694) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7f031ef25700 (LWP 36695) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7f031e724700 (LWP 36696) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7f031df23700 (LWP 36697) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7f031d722700 (LWP 36698) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f031cf21700 (LWP 36699) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7f02ff49c700 (LWP 36700) "gmain" 0x7f03214afaff in
__GI___poll (fds=0x55bd93ad1d90, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
10 Thread 0x7f02fec9b700 (LWP 36701) "gdbus" 0x7f03214afaff in
__GI___poll (fds=0x55bd93ae3ef0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
11 Thread 0x7f02f0861700 (LWP 36702) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
12 Thread 0x7f02e7066700 (LWP 36721) "dashboard" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
13 Thread 0x7f02e7fff700 (LWP 36774) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 13 (Thread 0x7f02e7fff700 (LWP 36774)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f03217a5623 in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f0321caa3ad in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7f0321781ad1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f0321595609 in start_thread (arg=) at
pthread_create.c:477
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139650458973952,
[Bug 1943352] [NEW] package docker.io 18.09.7-0ubuntu1~16.04.7 failed to install/upgrade: new docker.io package pre-installation script subprocess returned error exit status 1
Public bug reported: running do-release-upgrade from 16.04 I got the following: Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (495.5 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 99% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/docker.io/+filebug/8b8ceab2-1380-11ec-b34a-002481e7f48a?field.title=package+docker.io+18.09.7-0ubuntu1%7E16.04.7+failed+to+install%2Fupgrade%3A+new+docker.io+package+pre- installation+script+subprocess+returned+error+exit+status+1 You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): ^C === Command detached from window (Sun Sep 12 16:19:11 2021) === === Command terminated with signal 2 (Sun Sep 12 16:19:22 2021) === ProblemType: Package DistroRelease: Ubuntu 18.04 Package: docker.io 18.09.7-0ubuntu1~16.04.7 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Sun Sep 12 16:11:17 2021 ErrorMessage: new docker.io package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-03-25 (1632 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: docker.io Title: package docker.io 18.09.7-0ubuntu1~16.04.7 failed to install/upgrade: new docker.io package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2021-09-12 (0 days ago) ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943352 Title: package docker.io 18.09.7-0ubuntu1~16.04.7 failed to install/upgrade: new docker.io package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1943352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942378] Re: some programs dont display proper
** Attachment added: "Screenshot from 2021-08-30 23-07-32.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1942378/+attachment/5522411/+files/Screenshot%20from%202021-08-30%2023-07-32.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942378 Title: some programs dont display proper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1942378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942378] [NEW] some programs dont display proper
Public bug reported: even my activity to change the time ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1007.7-raspi 5.11.12 Uname: Linux 5.11.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 1 16:48:36 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:E9:1C:96 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image corruption hirsute raspi-image ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942378 Title: some programs dont display proper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1942378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942073] Re: [Dell][NorthBay] sound switch USB channel when do re-connect action
** Summary changed: - [Dell][South Peak 14] sound switch USB channel when do re-connect action + [Dell][NorthBay] sound switch USB channel when do re-connect action -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942073 Title: [Dell][NorthBay] sound switch USB channel when do re-connect action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom-hwe-18.04/+bug/1942073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942073] Re: [Dell][South Peak 14] sound switch USB channel when do re-connect action
update bug. ** Package changed: ubuntu => xf86-input-wacom-hwe-18.04 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942073 Title: [Dell][South Peak 14] sound switch USB channel when do re-connect action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom-hwe-18.04/+bug/1942073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
Did you remove or reconfigure any data disks before this bug appeared? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939950] Re: shim-signed fails to upgrade when NVMe drive is moved into the VM as Virtio drive
*** This bug is a duplicate of bug 1940723 *** https://bugs.launchpad.net/bugs/1940723 ** This bug has been marked a duplicate of bug 1940723 shim-signed fails to install if grub disk config is incorrect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939950 Title: shim-signed fails to upgrade when NVMe drive is moved into the VM as Virtio drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1939950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942073] [NEW] [Dell][South Peak 14] sound switch USB channel when do re-connect action
Public bug reported: [Summary] Monitor support HDMI and USB channel, [Reproduce steps] 1. connect system to monitor with type c to DP dongle and DP cable. 2. Connect system to monitor with USB type A to USB type B cable. 3. Connect 3.5mm audio combo jack headset. 4. Do shutdown, unplug/plug. sound can not keep on monitor speaker (HDMI). switch to USB speaker. [Results] Expected result Sound keep from monitor speaker(HDMI) Actual result Sound switch to USB speaker. [Additional Information] SKU ubuntu 18.04.5 LTS BIOS:1.10.1 Fail on monitor C2722DE, C2422HE. S2422HZ. S2722HZ. P2418HZ. Fail rate: 100/%. Monitor comment: fail on ubuntu 20.04. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: dell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942073 Title: [Dell][South Peak 14] sound switch USB channel when do re-connect action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1942073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
Are you using packer or anything else to modify the image? How are you modifying the disk layout? I'll double check against some of the provided VM sizes, but I don't think this is a problem with the image. It's likely a configuration issue...which is *not* to say it's not a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939950] Re: shim-signed fails to upgrade when NVMe drive is moved into the VM as Virtio drive
I don't believe this is a duplicate. shim-signed was looking for the NVMe storage that was removed and inaccessible. Bug #1940723 has a similar mechanism of failure, but is related to cloud instances, rather than a missing device. ** This bug is no longer a duplicate of bug 1940723 shim-signed fails to install if grub disk config is incorrect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939950 Title: shim-signed fails to upgrade when NVMe drive is moved into the VM as Virtio drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1939950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
Hi @abaelter, I'm from the Canonical Public Cloud team. I'll be looking into this further. Can you tell me what Azure VM size(s) you've observed this occurring on? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940136] Re: HyperV images do not include package manifests
** Merge proposal linked: https://code.launchpad.net/~codemouse92/livecd-rootfs/+git/livecd-rootfs/+merge/407212 ** Merge proposal linked: https://code.launchpad.net/~codemouse92/livecd-rootfs/+git/livecd-rootfs/+merge/407211 ** Merge proposal linked: https://code.launchpad.net/~codemouse92/livecd-rootfs/+git/livecd-rootfs/+merge/407210 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940136 Title: HyperV images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1940136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925954] Re: ERROR 8192: implode(): Passing glue string after array is deprecated. Swap the parameters at [/usr/share/libphutil/src/utils/utils.php:1572
@sylvestre This is a one-line fix that all my interns at MousePaw Media (where we use Arcanist daily) perform manually after installing. With Phacility winding down — don't worry, a community fork *is* spinning up — this is not likely to be fixed upstream of here. I think it'd be worth doing the one-line change here and opening the SRUs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925954 Title: ERROR 8192: implode(): Passing glue string after array is deprecated. Swap the parameters at [/usr/share/libphutil/src/utils/utils.php:1572 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phabricator/+bug/1925954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940136] [NEW] HyperV images do not include package manifests
Public bug reported: [Impact] * There are currently no manifests being produced for buildd tarballs in Hirsute, Focal, or Bionic. * Manifests _are_ being produced for the buildd tarballs in Impish. [Test Plan] * build the hyperv subproject * verify that the '*-desktop-hyperv.vhdx.zip' and '*-desktop- hyperv.vhdx.zip.manifest' artifacts are produced * verify that the packages listed in the manifests reflect the respective contents of each image [Where problems could occur] * There may be edge case where any automation not expecting this .manifest file may experience problems. (I find this unlikely, and the CPC processes do not have this issue.) [Other info] * This change involves a single line. Because the changelog modification was in the same commit, this line will probably need to be backported manually. ** Affects: livecd-rootfs (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/1940136 Title: HyperV images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1940136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939187] [NEW] package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4
Public bug reported: Error received on do-release-upgrade. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-63.71-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 7 01:21:35 2021 ErrorMessage: installed base-passwd package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-08 (1216 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: libc6 libc6 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.1.10ubuntu0.3 SourcePackage: base-passwd Title: package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to hirsute on 2021-08-06 (0 days ago) ** Affects: base-passwd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939187 Title: package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1939187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 ** Tags added: focal groovy hirsuit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929124] Re: When using webcam, CPU spikes to 100% for a few seconds, then drops, then recurs minutes later.
The attached graphic shows the behaviour of the CPU during the bug... while in a video call using the webcam, the CPU spikes (all cores at 100%) for a few seconds and then subsides. During that, the video that I'm sending is no longer viable with a lot of stops and starts and freezes, and I also can no longer understand the other participants on the call. This seems directly connected to webcam usage. The problem does not happen when the webcam is off. (This obviously isn't a viable permanent solution.) It also isn't consistent... the CPU will spike for a few seconds and then go back to normal levels. The spike doesn't seem to be connected to anything I'm doing or not doing during the call. This feels like perhaps the CPU and the webcam are somehow buffering or packaging a lot of info at once? The program that is shown with the highest CPU usage is whatever program is using the webcam. Zoom, or the browser if it's a browser-based video meeting. ** Attachment added: "Graphic of the CPU spiking during a web call" https://bugs.launchpad.net/ubuntu/+bug/1929124/+attachment/5506553/+files/cpu%20spiking%20during%20web%20call%202.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929124 Title: When using webcam, CPU spikes to 100% for a few seconds, then drops, then recurs minutes later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1929124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10
I tried to reproduce using the same read-dpcd as above on #11. I don't see the hang anymore using 5.4 on 20.04. Thanks for following up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826691 Title: fwupd hangs after 19.04 upgrade from 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805543] Re: Packaged version of iptables doesn't provide --random-fully flag.
Should this be higher priority? https://tech.xing.com/a-reason-for-unexplained-connection-timeouts-on-kubernetes-docker-abd041cf7e02 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805543 Title: Packaged version of iptables doesn't provide --random-fully flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1805543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817350] Re: Running 'aptitude update' clears hold flags on packages
Every time I run aptitude update, the /var/lib/aptitude/pkgstates is updated again, so I guess a change in behavior from 18.04 perhaps! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817350 Title: Running 'aptitude update' clears hold flags on packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1817350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817350] Re: Running 'aptitude update' clears hold flags on packages
This affects 20.04 as well, as it actually happens every time aptitude update is executed. This effectively makes apt-mark hold pointless for me! ops@d-vgt-006:~$ sudo apt-mark hold unattended-upgrades unattended-upgrades set on hold. ops@d-vgt-006:~$ sudo apt-mark showhold unattended-upgrades ops@d-vgt-006:~$ sudo aptitude update Hit http://us.archive.ubuntu.com/ubuntu focal InRelease Hit http://us.archive.ubuntu.com/ubuntu focal-updates InRelease Hit http://us.archive.ubuntu.com/ubuntu focal-backports InRelease Hit http://security.ubuntu.com/ubuntu focal-security InRelease ops@d-vgt-006:~$ sudo apt-mark showhold ops@d-vgt-006:~$ ops@d-vgt-006:~$ sudo apt-mark showhold ops@d-vgt-006:~$ sudo apt-mark hold unattended-upgrades unattended-upgrades set on hold. ops@d-vgt-006:~$ sudo apt-mark showhold unattended-upgrades ops@d-vgt-006:~$ sudo aptitude update Hit http://us.archive.ubuntu.com/ubuntu focal InRelease Hit http://us.archive.ubuntu.com/ubuntu focal-updates InRelease Hit http://us.archive.ubuntu.com/ubuntu focal-backports InRelease Hit http://security.ubuntu.com/ubuntu focal-security InRelease ops@d-vgt-006:~$ sudo apt-mark showhold ops@d-vgt-006:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817350 Title: Running 'aptitude update' clears hold flags on packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1817350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762672] Re: TPM intermittently fails after cold-boot
After upgrading from 18.04 to 21.04, my XPS 13 fails to boot, giving the message "a TPM error (2314) occurred attempting the self test". How can this be fixed? Thanks, jason -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929124] Re: When using webcam, CPU spikes to 100% for a few seconds, then drops, then recurs minutes later.
Note to bot comment: I cannot determine what source packages are involved because I when the problem occurs the CPU spike happens within the program using the webcam. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929124 Title: When using webcam, CPU spikes to 100% for a few seconds, then drops, then recurs minutes later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1929124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929124] [NEW] When using webcam, CPU spikes to 100% for a few seconds, then drops, then recurs minutes later.
Public bug reported: The CPU will spike to 100% when using the webcam, then return to normal. This has happened in Firefox with Google Meet, and in Zoom. Trying to catch in the system monitor the program running at 100% is usually 'Web Content' or Firefox or Zoom, if those are the programs I'm using at the time. When I turn off the webcam in Google Meet, the problem did not recur. 1) Description:Ubuntu 20.04.2 LTS Release:20.04 2) unsure of package, as this appears to be happening with the webcam, even though it is showing high CPU on the program being used for meetings. 3) not continual 100% CPU spikes! Normal video meeting activity. 4) CPU spiking to 100% for a few seconds, then dropping back, then recurring. Experiencing this on an Asus Zenbook UX330UAK ** Affects: 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/1929124 Title: When using webcam, CPU spikes to 100% for a few seconds, then drops, then recurs minutes later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1929124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown
Also see this on 20.10 on a Dell XPS 15 9550. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280300 Title: Desktop contents displayed on resume, before lock screen is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928521] [NEW] coqide package should require adwaita-icon-theme-full
Public bug reported: I've recently discovered (https://github.com/coq/coq/issues/14324) that coqide requires adwaita-icon-theme-full to display icons correctly. It seems to me this dependency is not recorded in the ubuntu package. ** Affects: coq (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/1928521 Title: coqide package should require adwaita-icon-theme-full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coq/+bug/1928521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914106] Re: Xorg freeze
If the problem recurs, can this be reopened? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914106 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914106] Re: Xorg freeze
Okay! I removed the extensions using the above commands, and booted back into the X11 'normal' Ubuntu option. No freezes after checking some of the main actions that precipitated a freeze before. (Opening a window, trying to choose 'suspend' from the power options) I've re-installed some of the key gnome extensions I wanted, and still seeing no freeze currently in X11! I'll update here if there are any changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914106 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926080] [NEW] package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Bug splat occurs on startup. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: initramfs-tools 0.137ubuntu12 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Apr 18 17:53:40 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: initramfs-tools Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926080 Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1926080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925742] Re: IMAP broken in Evolution
Bug is also present in Groovy and Hirsute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: IMAP broken in Evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923272] [NEW] package is unbackportable to old i386 systems
Public bug reported:
The patch file 0006-Disable-DT_TEXTREL-warnings-on-Linux-i386.patch is
inadequate because it updates configure.ac without updating configure. It
should instead read something like
```
diff --git a/configure b/configure
index 74657d2..c1215b4 100755
--- a/configure
+++ b/configure
@@ -13899,6 +13899,18 @@ case $arch in #(
esac ;;
esac
+# Disable DT_TEXTREL warnings on Linux i386
+# See https://github.com/ocaml/ocaml/issues/9800
+
+case $host in #(
+ i?86-*-linux-*) :
+common_cflags="-Wl,-z,notext $common_cflags"
+mksharedlib="$mksharedlib -Wl,-z,notext"
+mkmaindll="$mkmaindll -Wl,-z,notext" ;; #(
+ *) :
+ ;;
+esac
+
# Assembler
if test -n "$host_alias"; then :
diff --git a/configure.ac b/configure.ac
index aa5f26f..f43eaa4 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1015,6 +1015,16 @@ AS_CASE([$arch],
[common_cflags="-no-pie $common_cflags"],
[])])
+# Disable DT_TEXTREL warnings on Linux i386
+# See https://github.com/ocaml/ocaml/issues/9800
+
+AS_CASE([$host],
+ [i?86-*-linux-*],
+[common_cflags="-Wl,-z,notext $common_cflags"
+mksharedlib="$mksharedlib -Wl,-z,notext"
+mkmaindll="$mkmaindll -Wl,-z,notext"],
+ [])
+
# Assembler
AS_IF([test -n "$host_alias"], [toolpref="${host_alias}-"], [toolpref=""])
```
** Affects: ocaml (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/ocaml/ocaml/issues #9800
https://github.com/ocaml/ocaml/issues/9800
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923272
Title:
package is unbackportable to old i386 systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ocaml/+bug/1923272/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923272] Re: package is unbackportable to old i386 systems
See also https://github.com/ocaml/ocaml/issues/9800#issuecomment-786868875 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923272 Title: package is unbackportable to old i386 systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocaml/+bug/1923272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1914106] Re: Xorg freeze
Aha! I disabled the extensions but didn't think to fully remove them. ~Jason pronouns: he / him / his jmeh...@gmail.com | www.jasonmehmel.com On Mon, 5 Apr 2021 at 23:20, Daniel van Vugt <1914...@bugs.launchpad.net> wrote: > Thanks but that log is full of errors from extensions. Please follow > step 1 in comment #2 and also remove locally installed extensions: > > cd /home/jason/.local/share/gnome-shell > rm -rf extensions > > Then reboot and if the problem persists follow steps 2 & 3 again. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1914106 > > Title: > Xorg freeze > > Status in Ubuntu: > Incomplete > > Bug description: > I am not finding this problem in Wayland, just X11 / Xorg > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 > Uname: Linux 5.4.0-65-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu27.14 > Architecture: amd64 > CasperMD5CheckResult: skip > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Feb 1 11:48:27 2021 > DistUpgraded: 2020-09-20 17:26:20,447 ERROR got error from > PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to > execute child process “./xorg_fix_proprietary.py” (No such file or > directory) (8)) > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: >nvidia, 390.141, 5.4.0-64-generic, x86_64: installed >nvidia, 390.141, 5.4.0-65-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GpuHangFrequency: Continuously > GpuHangReproducibility: Yes, I can easily reproduce it > GpuHangStarted: Immediately after installing this version of Ubuntu > GraphicsCard: >Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1520] > InstallationDate: Installed on 2017-07-04 (1308 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > MachineType: ASUSTeK COMPUTER INC. UX330UAK > ProcEnviron: >LANGUAGE=en_CA:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_CA.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic > root=UUID=1778a8fc-a0e5-4815-9737-655369bac47b ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: Upgraded to focal on 2020-09-20 (133 days ago) > dmi.bios.date: 04/19/2019 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX330UAK.315 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX330UAK > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX330UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook > dmi.product.name: UX330UAK > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > xserver.bootTime: Mon Sep 21 15:47:24 2020 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.20.8-2ubuntu2.4 > xserver.video_driver: modeset > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1914106/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914106 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914106] Re: Xorg freeze
Trying to boot into the Xorg (or default?) Ubuntu and still experiencing the same freezing issue. Every time I try to lock or suspend the screen, everything seems to freeze. I can still move the mouse but nothing I click on appears to have any effect. The freeze doesn't seem to resolve given time, either. ** Attachment added: "the prevboot text file as requested." https://bugs.launchpad.net/ubuntu/+bug/1914106/+attachment/5483616/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914106 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914106] Re: Xorg freeze
Trying step 3 first, and when trying to run ubnutu-bug on the .crash file I get a dialog box: "Ubuntu 20.04 has experienced an internal error. Send problem report to the developers?" Inside the details, I see the 'unreportable reason' as: You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs: ubuntu-keyring. I'm not sure if this is connected to the freeze issue, but I thought I'd try the crash reports before I did my reboot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914106 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916716] Re: pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes()
Applied available updates and the updates appear to fix this bug.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916716 Title: pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes() To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1916716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915304] Re: linux-stable v4.14.217 causes skb_mark_not_on_list() build failure
I wish you'd not waste time on this downstream stuff. wireguard-linux- compat v1.0.20210219 has the proper fix (along with other important fixes). Simply import the package from debian and be done with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915304 Title: linux-stable v4.14.217 causes skb_mark_not_on_list() build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard-linux-compat/+bug/1915304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915304] Re: linux-stable v4.14.217 causes skb_mark_not_on_list() build failure
Due to inconsistent use of ubuntu-specific identifiers and complexity introduced HWE and such, wireguard-linux-compat develops against the latest kernels for each of the Ubuntu releases -- listed on https://www.wireguard.com/build-status/ , ctrl+F for ubuntu. This already amounts to ~7 kernels. So the thing to do here would be to add !defined(ISUBUNTU1804) to the relevant ifdef: #if (LINUX_VERSION_CODE < KERNEL_VERSION(4, 19, 10) && LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0) && !defined(ISRHEL8) && !defined(ISUBUNTU1804)) || LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 217) Afterwards, if you want to apply additional patches downstream so that this works on older kernels within each Ubuntu release, that would make sense. But upstream should first always be made to work against the latest kernel version in each Ubuntu release. If you have advanced knowledge that something is about to break (because of this or that backport), then please push a patch upstream for that. apw@ knows how this works, if you want to talk to somebody internal about it. Otherwise I'm zx2c4 on Freenode and happy to help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915304 Title: linux-stable v4.14.217 causes skb_mark_not_on_list() build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard-linux-compat/+bug/1915304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915304] Re: linux-stable v4.14.217 causes skb_mark_not_on_list() build failure
This was fixed in the latest upstream wireguard-linux-compat release on Jan 24. ** Changed in: wireguard-linux-compat (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/1915304 Title: linux-stable v4.14.217 causes skb_mark_not_on_list() build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard-linux-compat/+bug/1915304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Project changed: ubuntu-cdimage => ubuntubudgie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914963] [NEW] Unable to upgrade to 20.04, could not calculate upgrade.
Public bug reported: I'm currently using Ubuntu 18.04.5 LTS and I'm trying to upgrade to 20.04. I keep getting the 'could not calculate upgrade' error. I have searched through bug reports exhaustively and cannot find the solution. I have no broken packages according to apt and aptitude. I don't know what to do. I've removed everything that shows up in previous bug reports as causing problems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Feb 7 15:20:03 2021 InstallationDate: Installed on 2019-03-12 (698 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-02-07 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914963 Title: Unable to upgrade to 20.04, could not calculate upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1914963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914106] [NEW] Xorg freeze
Public bug reported: I am not finding this problem in Wayland, just X11 / Xorg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 11:48:27 2021 DistUpgraded: 2020-09-20 17:26:20,447 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1520] InstallationDate: Installed on 2017-07-04 (1308 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. UX330UAK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=1778a8fc-a0e5-4815-9737-655369bac47b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-09-20 (133 days ago) dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX330UAK.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX330UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX330UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX330UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Sep 21 15:47:24 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914106 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1914106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890432] Re: Create subnet is failing under high load with OVN
sub'd to field high, this is affecting sqa release testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890432 Title: Create subnet is failing under high load with OVN To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-api/+bug/1890432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820171] Re: Screen blank when watching youtube on Chromium
How to reproduce this bug is to install any supported version of Lubuntu, connect to the internet, turn on a youtube video, in firefox (chromium and chrome from other bug reports should work as well) and then wait for 15 minutes. The expected behavior is for the operating system to recognize that media is playing and not to blank/screensave/lock the screen and to continue to serve media. The behavior experienced is for the screen to blank, a screensaver to come up, or the screen to lock, and or power off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820171 Title: Screen blank when watching youtube on Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1820171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
