[Bug 1728651] Re: Intel(R) Dual Band Wireless AC 8260, REV=0x208 [8086:24f3] subsystemid [8086:0010]: System hangs after iwlwifi firmware crash
I'm actually still using this laptop, on WiFi, and it regularly stays up for a fortnight between minor kernel updates, so I think we can confidently say this bug is fixed for me, on Jammy. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728651 Title: Intel(R) Dual Band Wireless AC 8260, REV=0x208 [8086:24f3] subsystemid [8086:0010]: System hangs after iwlwifi firmware crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1728651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076951] Re: v4l2loopback-dkms 0.12.7-2ubuntu2~22.04.1: v4l2loopback kernel module failed to build
Happened while running automated software update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076951 Title: v4l2loopback-dkms 0.12.7-2ubuntu2~22.04.1: v4l2loopback kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/2076951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072440] Re: A semi-transparent orange band covers the top of display
Additional symptoms: - The color of the band changes based on the color chosen om the Settings>Appearance - Minimizing the active window and then maximizes the window and no color band for all windows, so that's a work-around but not a fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072440 Title: A semi-transparent orange band covers the top of display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-session-utils/+bug/2072440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072440] Re: A semi-transparent orange band covers the top of display
Is the display kernel, gnome, or X? The Ubuntu 24.04 documentation does not make that clear. From the docs I am guessing Gnome. ** Package changed: ubuntu => x11-session-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072440 Title: A semi-transparent orange band covers the top of display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-session-utils/+bug/2072440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2031198] Re: Alienware 15 R3 boots to black after upgrade to 22.04, Cannot use other TTY interfaces either (ctrl+alt+f2, etc)
Sory, xashyar, I never got this resolved. The nvidia bug https://forums.developer.nvidia.com/t/x-hangs-blocked-on-nvidia-modeset- in-ubuntu-22-02-nvidia-drivers-535/264035/6 devolved into "your laptop sucks" peacocking and i've just relegated the poor machine to windows- gaming-only duty. I haven't tried anything linux on that machine since August of last year. (so maybe my particular problem has been fixed by something in the interval?) My behavior doesn't look like what you describe in https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-535/+bug/2071680, though. I *always* got a grub menu. The problem would always happen after grub. It looks like something in your issue also sometimes prevents grub from showing up? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2031198 Title: Alienware 15 R3 boots to black after upgrade to 22.04, Cannot use other TTY interfaces either (ctrl+alt+f2, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2031198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072440] [NEW] A semi-transparent orange band covers the top of display
Public bug reported: Intermittently 5- to 20-minutes after boot, a semi-transparent orange band overlays whatever is being displayed. I have a screen shot of it. This is a new installation of 24.04 LTS on a new-to-me computer. It is dual-bppt with Win10 and Windows does not have that behavior. The only remedy is to restart. My main computer uses 22.04 so 24.04 is new to me. Static hostname: lb-hp-15 Icon name: computer-laptop Chassis: laptop 💻 Machine ID: 81b4ae228ed846b6a7773c213d34d9d7 Boot ID: ae95ec7464394563b9f0a05174745da7 Operating System: Ubuntu 24.04 LTS Kernel: Linux 6.8.0-36-generic Architecture: x86-64 Hardware Vendor: Hewlett-Packard Hardware Model: HP 15 TS Notebook PC Firmware Version: F.36 Firmware Date: Thu 2014-12-18 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: 24.04 ** Tags added: 24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072440 Title: A semi-transparent orange band covers the top of display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069763] [NEW] Ubuntu 24.04 Openshot 3.1.1 fails to export video content
Public bug reported: Openshot 3.1.1 of Ubuntu 24.04 fails to export video content (only audio). Replication: File - export project - export video - select MP4 (h.264) - export video Actual result: mp4 file is created with audio only Expected result: mp4 file is created with video and audio. This bug has been reported previously; https://github.com/OpenShot/openshot-qt/issues/5300 https://www.reddit.com/r/OpenShot/comments/1d4256l/video_is_not_exporting/ https://www.reddit.com/r/OpenShot/comments/1af1ezi/openshot_only_exports_audio_on_black_screen/ The current solution involves uninstalling openshot, then downloading and executing the latest daily build of openshot 3.1.1; https://www.openshot.org/download/#daily (e.g. 8 June 2024) sudo apt remove openshot chmod 755 OpenShot-v3.1.1-dev-daily-12440-9424cc0c-5e9fa273-x86_64.AppImage execute OpenShot-v3.1.1-dev-daily-12440-9424cc0c-5e9fa273-x86_64.AppImage ** Affects: openshot-qt (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/2069763 Title: Ubuntu 24.04 Openshot 3.1.1 fails to export video content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openshot-qt/+bug/2069763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069743] [NEW] Ubuntu 24.04 7zip v23.01 multi-part zip archive error
Public bug reported: 7zip v23.01 released with Ubuntu 24.04 (Nobel) throws an error when creating multi-part zip archives: This bug has been reported on sourceforge; https://sourceforge.net/p/sevenzip/bugs/2407/ Replication instructions: Assume fileName.gz is larger than 150MB, and wish to create a multi-part zip archive (archive.zip.001, archive.zip.002 etc); 7z a -tzip -v150M archive.zip fileName.gz Actual result: System ERROR: errno=17 : File exists Expected result: Everything is Ok Confirmed the bug is not present in the version of 7zip released with Ubuntu 22.04 (Jammy); download jammy p7zip packages; https://packages.ubuntu.com/jammy/p7zip-full https://packages.ubuntu.com/jammy/p7zip sudo apt remove 7zip sudo dpkg -i p7zip_16.02+dfsg-8_amd64.deb p7zip-full_16.02+dfsg-8_amd64.deb ** Affects: p7zip (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/2069743 Title: Ubuntu 24.04 7zip v23.01 multi-part zip archive error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p7zip/+bug/2069743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
So this has been closed because it is fixed in 24.04, except that overnight this behaviour is now occurring in 24.04. Overnight my Gnome Online Accounts simply disappeared. When I attempt to re-establish them the GOA tool in settings opens my browser, I follow the onscreen prompts and the last screen to add the account to Ubuntu just keeps loading forever, and the Setting windows freezes and requires a force quit. This is an action replay of what happened in 22.04, and it appears I will have to abandon Evolution as my email client and revert to Thunderbird again unless somebody can suggest a fix to GOA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065559] [NEW] duply fetch not compatible with shipped duplicity
Public bug reported: The versions of duply (2.4.1) and duplicity (2.1.4) shipped in 24.04 are not fully compatible. Backing up works, but when running 'duply fetch ' I get the following error: ``` --- Start running command FETCH at 2024-05-13 08:51:44.314 --- CommandLineError: Option '--file-to-restore was changed in 2.0.0. --file-to-restore to --path-to-restore --do-not-restore-ownership to --no-restore-ownership Enter 'duplicity --help' for help screen. ``` This seems to be fixed in the current upstream version of duply (2.5.2). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: duply 2.4.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon May 13 08:52:54 2024 InstallationDate: Installed on 2024-04-26 (17 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424.2) PackageArchitecture: all SourcePackage: duply UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: duply (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065559 Title: duply fetch not compatible with shipped duplicity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duply/+bug/2065559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1992235] Re: Screen freeze
I've been using wayland since zoom started supporting it, so I haven't seen this freeze a year. I think this can probably be closed. Thanks, Bruce On 07/03/2024 10:44, Scarlett Gately Moore wrote: > Is this still an issue? > > ** Changed in: kwin (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1992235 Title: Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1992235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
All autopackage tests succeeded after multiple trials. Canonical customer with golang client against openssl server, where bug was first noticed, will be testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Several of the autopkgtest failures are due to response issues (e.g.curl: (7) Failed to connect to launchpad.net port 443: Connection timed out) so I'm going to ask that they be run again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Please note the manual testing using the trace option shows the same results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Attach debdiff relative to 18.04.17: openssl (1.1.1-1ubuntu2.1~18.04.17ubuntu1) bionic; urgency=medium * Backport pr9780: - d/p/pr9780_0001-Don-t-send-a-status_request-extension-in-a-Certifica.patch - d/p/pr9780_0002-Teach-TLSProxy-how-to-parse-CertificateRequest-messa.patch -- Bruce Elrick Mon, 09 May 2022 19:38:43 + ** Patch added: "openssl_1.1.1-1ubuntu2.1~18.04.17ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+attachment/5587970/+files/openssl_1.1.1-1ubuntu2.1~18.04.17ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Thanks for the update, Marc. I will work on producing the dsc against 1.1.1-1ubuntu2.1~18.04.17. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
I re-ran the test as follows to actually test the server side with only the packaged executables. I used this command for the server side: /usr/bin/openssl s_server -key key.pem -cert cert.pem -status_file openssl-1.1.1/test/recipes/ocsp-response.der -Verify 5 with ldd showing it loading its ssl & crypt libraries from /usr/lib/x86_64-linux-gnu: ldd /usr/bin/openmssl linux-vdso.so.1 (0x7ffe6ee65000) libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x7f44027c4000) libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x7f44022f9000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f44020da000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4401ce9000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f4401ae5000) /lib64/ld-linux-x86-64.so.2 (0x7f4402d04000) I built the client from 18.06.16 source with tracing enabled and used it for both tests and ran it with this command: LD_LIBRARY_PATH=openssl-1.1.1/build_shared openssl-1.1.1/build_shared/apps/openssl s_client -status -trace -cert cert.pem -key key.pem with ldd showing it loading its own libraries: LD_LIBRARY_PATH=openssl-1.1.1/build_shared ldd openssl-1.1.1/build_shared/apps/openssl linux-vdso.so.1 (0x7fff51ff9000) libssl.so.1.1 => openssl-1.1.1/build_shared/libssl.so.1.1 (0x7fc8c28b4000) libcrypto.so.1.1 => openssl-1.1.1/build_shared/libcrypto.so.1.1 (0x7fc8c23e9000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fc8c21ca000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc8c1dd9000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fc8c1bd5000) /lib64/ld-linux-x86-64.so.2 (0x7fc8c2dfe000) The following logs show the difference between having: ii openssl1.1.1-1ubuntu2.1~18.04.15 amd64Secure Sockets Layer toolkit - cryptographic utility and having: ii openssl1.1.1-1ubuntu2.1~18.04.16 amd64Secure Sockets Layer toolkit - cryptographic utility ubuntu@bionic-lp-1940141:~$ grep -B1 -A4 CertificateRequest s_client-18.04.16-from-source-with-trace_server-18.04.15-from-package.log Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. ubuntu@bionic-lp-1940141:~$ grep -B1 -A4 CertificateRequest s_client-18.04.16-from-source-with-trace_server-18.04.16-proposed-from-package.log Inner Content Type = Handshake (22) CertificateRequest, Length=45 request_context (len=0): extensions, length = 42 extension_type=signature_algorithms(13), length=38 ecdsa_secp256r1_sha256 (0x0403) This is indicative of the fix working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
The user who discovered this bug using the golang TLS implementation will be testing the proposed package within the week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
I should add, the results in comment 22 indicate that the fix is active and working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
I pulled the proposed source: $ pull-lp-source openssl bionic built with tracing enabled: $ cd openssl-1.1.1 $ sed -i -e '/^CONFARGS =/a CONFARGS += enable-ssl-trace' debian/rules $ debuild -us -uc -b 2>&1 | tee ../debuild.log $ cd .. installed: $ sudo dpkg -i libssl1.1_1.1.1-1ubuntu2.1~18.04.16_amd64.deb openssl_1.1.1-1ubuntu2.1~18.04.16_amd64.deb tested: $ openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout key.pem -out cert.pem $ openssl s_server -key key.pem -cert cert.pem -status_file openssl-1.1.1/test/recipes/ocsp-response.der -Verify 5 2>&1 | tee s_server.log & $ openssl s_client -status -trace -cert cert.pem -key key.pem 2>&1 | tee s_client.log (^c) $ grep -B1 -A4 CertificateRequest s_client.log Inner Content Type = Handshake (22) CertificateRequest, Length=45 request_context (len=0): extensions, length = 42 extension_type=signature_algorithms(13), length=38 ecdsa_secp256r1_sha256 (0x0403) $ tail -6 s_server.log --- No server certificate CA names sent CIPHER is TLS_AES_256_GCM_SHA384 Secure Renegotiation IS supported ERROR -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968728] Re: LibreOffice popups don't open on Wayland in KDE
This fixes the issue for me. Thank you so much! 😊 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968728 Title: LibreOffice popups don't open on Wayland in KDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968728] [NEW] LibreOffice popups don't open on Wayland in KDE
Public bug reported: In Kubuntu 22.04 beta, LibreOffice Calc drop-down popups are not displaying. For example, font size or autofilter. There is an upstream fix: https://bugs.documentfoundation.org/show_bug.cgi?id=144585 ** Affects: libreoffice (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/1968728 Title: LibreOffice popups don't open on Wayland in KDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968599] [NEW] plasma-integration can't connect when running firefox snap
Public bug reported: Since upgrading to ubuntu 22.04 beta, I have been unable to use the plasma-integration addon in Firefox. It says "Failed to connect to the native host Make sure that the plasma-integration package is correctly installed and that you are running Plasma 5.13 or later No such native application org.kde.plasma.browser_integration" plasma-integration is indeed installed and version > 5.13: ii plasma-desktop 4:5.24.4-0ubuntu1 amd64Tools and widgets for the desktop ii plasma-integration 5.24.4-0ubuntu1 amd64Qt Platform Theme integration plugins for KDE Plasma The problem can be fixed by installing the native application in the snap package: https://community.kde.org/Plasma/Browser_Integration Thanks ** Affects: firefox (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/1968599 Title: plasma-integration can't connect when running firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1968599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966066] Re: audio from external sound card is distorted
5.13.0-39-generic still has this problem. Focusrite 2i2 I suppose the test patch for -37 will not work for this case. Might need to roll back to 5.4 generic, cannot have this device offline. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966066 Title: audio from external sound card is distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Marc, I lean your way in terms of my feel for the likelihood that someone is relying on incorrect behaviour in bionic/openssl-1.1.1. I can say that while the lp1940141* patches rely on the pr9780 ones, the reverse is absolutely not the case and thus the lp1940141 ones could be dropped as a whole to achieve the functional portion of the backport without it being optional. But I leave that decision to those with more experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Good point, Dan. A caveat to my work here on this patch: I did some C programming and played with the Perl test harness in the early 90s which gave me enough abililty to develop this patch set but I would benefit from any deeper knowledge someone else may have, especially anyone with openssl knowledge. In terms of due dilligance, I've searched through the source files for references to 'TSProxy' which is the parent directory for a number of the test hardness perl modules changes in the commit and nothing I find indicates it is referenced by the actual openssl C code but only is part of the build/test process. For extra due diligence I built with only the tests change backported and two tests fail. Tests failing is expected because the actual functional backport is missing. When I add the functional backport then all tests succeed, as expected. When I then make the test optional, the same two tests fail, as expected. See the test-results.txt attachment for more. I fix the tests by enabling the fix for 'Test 6' only in openssl-1.1.1/test/recipes/70-test_tls13messages.t by wrapping the test with perl code to set and delete the FIX_LP_1940141 environment variable. As an aside, I now see that other such env var setting does not use single-quoted strings but rather just bare strings; this is allowed in perl and my patch does not followed the style in the rest of the test file. My understanding is that there are several flags for subtests, thus accounting for the two passing or failing. But more to your point about the risk of backporting the tests, my assessment is that the perl modules are only in testing and while there are a non-trivial number of tests added along with the one that tests what is being backported, the fact that they all pass suggests that they are relevant here. That is, it looks to me these additional tests are not-inappropriate, are actually appropriate, and in fact the reason they were added later was this fix forced the issue on the lack of capability in the test coverage. ** Attachment added: "test-results.txt" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+attachment/5572296/+files/test-results.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
It's not needed for actual functionality of the backport but that assumes that any future backports or fixes don't break this backport. By adding the tests (and wrapping the one test that fails when the backport-enabling environment variable is not set with the enabling of that environmetn variable, we ensure that and future changes don't break this change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
"variable, we" -> "variable) we" "and future" -> "any future" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Hey Dan Streetman (ddstreet), I believe the above patch satisfies your valid concerns about backporting. Would you please analyse for acceptance? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
openssl (1.1.1-1ubuntu2.1~18.04.15ubuntu1) bionic; urgency=medium * Backport pr9780 but make it optional: - d/p/pr9780_0002-Teach-TLSProxy-how-to-parse-CertificateRequest-messa.patch - d/p/pr9780_0001-Don-t-send-a-status_request-extension-in-a-Certifica.patch - d/p/lp1940141-make-pr-9780-optional.patch - d/p/lp1940141-fix-tests-accordingly.patch - d/p/lp1940141-update-manpages.patch -- Bruce Elrick Wed, 16 Mar 2022 17:05:32 + ** Patch added: "Backport pr9780 but make it optional" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+attachment/5570447/+files/bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
For posterity, here is an example of the relevant part of the client trace output when the bug is active, i.e. data is sent with the ClientRequest: $ grep -B1 -A4 CertificateRequest s_client.log Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. Here is an example of the relevant part of the client trace output when this is fixed: $ grep -B1 -A4 CertificateRequest s_client.log Inner Content Type = Handshake (22) CertificateRequest, Length=45 request_context (len=0): extensions, length = 42 extension_type=signature_algorithms(13), length=38 ecdsa_secp256r1_sha256 (0x0403) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964950] [NEW] installer crashed
Public bug reported: kubuntu@kubuntu:~$ ubuntu-bug ubiquity ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 13:21:27.879: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 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 CasperVersion: 1.467 CurrentDesktop: KDE Date: Tue Mar 15 13:21:15 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220315) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ubiquity-22.04.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964950 Title: installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1964950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964828] [NEW] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
Public bug reported: ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 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 CasperVersion: 1.467 CurrentDesktop: KDE Date: Mon Mar 14 21:22:23 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ubiquity-22.04.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964828 Title: ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist- packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general- hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1964828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960141] Re: Ubiquity Bug: forces Uefi options. I need MBR not GPT.
I went through a fresh install. Here are the details:
Using a new image of Ubuntu 21.10.
Download ISO. Verify using checksum. Use "USB Image writer" on virgin 32GB
Stick. gdisk shows stick has 3 partitions: Basic, EFI, and Basic. MBR is
protective, GPT is present.
Format 120GB SSD to Fat32. Box BIOS is set to "NO EFI". Installation
proceeded using all defaults. Reboot.
Boot message "Boot Failure". Go to F10 screen and select hard drive: Normal
Startup.
Replace disk with a Ubuntu 20.04.2 hard drive: System boots normally without
any failure message.
Data 1:
GPT fdisk (gdisk) version 1.0.8
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Model: ADATA SU655
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 2AA7FA81-FDCB-4C2D-BF94-267833FC182A
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2-sector boundaries
Total free space is 16 sectors (8.0 KiB)
Number Start (sector)End (sector) Size Code Name
1 341987 977.0 KiB EF02
21988 1052769 513.1 MiB EF00 EFI System Partition
3 1052770 234441598 111.3 GiB 8300
DATA 2
{
"Version": "21.10",
"BIOS": {
"Vendor": "Intel Corp.",
"Version": "TYG4110H.86A.0036.2009.1126.2047"
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "4",
"Threads": "1",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "23",
"Stepping": "10",
"Name": "Intel(R) Core(TM)2 Quad CPUQ9400 @ 2.66GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"HwCap": "-",
"GPU": [
{
"Vendor": "8086",
"Model": "2e32"
}
],
"RAM": 8.1,
"Disks": [
120
],
"Partitions": [
114.3,
0.5
],
"Screens": [
{
"Size": "530mmx290mm",
"Resolution": "1920x1080",
"Frequency": "59.96"
},
{
"Size": "410mmx230mm",
"Resolution": "1366x768",
"Frequency": "59.62"
}
],
"Autologin": true,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/New_York",
"Install": {
"Media": "Ubuntu 21.10 \"Impish Indri\" - Release amd64 (20211012)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "use_device",
"DownloadUpdates": true,
"Language": "en",
"Minimal": false,
"RestrictedAddons": false,
"Stages": {
"0": "language",
"1": "language",
"566": "console_setup",
"590": "prepare",
"607": "partman",
"631": "start_install",
"749": "timezone",
"770": "usersetup",
"1053": "user_done",
"1574": "done"
}
}
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960141
Title:
Ubiquity Bug: forces Uefi options. I need MBR not GPT.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960141/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960141] Re: Ubiquity Bug: forces Uefi options. I need MBR not GPT.
** Package changed: ubuntu => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960141 Title: Ubiquity Bug: forces Uefi options. I need MBR not GPT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960141] [NEW] Ubiquity Bug: forces Uefi options. I need MBR not GPT.
Public bug reported: Unless I use F10 and Select, I get “no bootable disk” message from my BIOS. I’ve installed separate disks with other Op systems … no problems. (Ubuntu 20.04, Mint 20.1, Zorin 16, Fedora 35, etc). It seems UB install forces Uefi options. Not good. I need Bios mode or legacy mode. I have disabled Uefi in my bios. The UB makes my disk install type GPF. Unless I use F10 and select an option, I get a no bootable disk message from my BIOS. If I press F10, when the screen says, "Please select boot device", I can select the hard drive and the Ubuntu boot screen proceeds normally. Only 21.10, Budgie 21.10, and unsupported 22.04 show this problem. I’ve installed separate disks with other operating systems without any problems. Ubuntu 20.04, Mint 20.1, Zorin 16, and Fedora 35, all work fine. I have disabled UEFI in my BIOS and I have also tried the "Something Else" option during installation. I've followed the Ubuntu Handbook for installation. My hard drive has only 2 partitions: "sda1 core.img and sda2 ext4 /". How can I boot Ubuntu without having to use F10 and select the appropriate drive? Using gdisk, I found that the disk was still in GPT mode in spite of my changes. I then started over and using gparted created the following MBR disk table: Number Start (sector)End (sector) Size Code Name 12048 34815 16.0 MiB0700 Microsoft basic data 2 3481662543871 29.8 GiB8300 Linux filesystem 36254387296098303 16.0 GiB8200 Linux swap 496098304 625141759 252.3 GiB 8300 Linux filesystem I then did a fresh install of Budgie 21.10 and chose “something else”. I had to bypass 5 error messages trying to convince me that EFI was missing. (I knew that!) The install went normally and the computer boots and works perfectly. Note: there is an option in gdisk to convert GPT to MBR but I couldn’t make it work. I also left the problem on the AskUbuntu site but have not gotten any replies. I next tried it on Ubuntu 21.10. Works fine. This MSDOS table can be much simpler: A 16MB boot partition and the rest an EXT4 root partition. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: installation mbr ** Summary changed: - Ubiquity Bug: forces Uefi options. I need MBR not GPF. + Ubiquity Bug: forces Uefi options. I need MBR not GPT. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960141 Title: Ubiquity Bug: forces Uefi options. I need MBR not GPT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956263] Re: Situationm
Thanks for getting back to me. Can you recommend one or two books to help? On Mon, Jan 3, 2022, 8:55 PM Chris Guiver <1956...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > Unfortunately, we cannot work on this bug because your description > didn't include enough information. You may find it helpful to read "How > to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > We have instructions on debugging some types of problems at > http://wiki.ubuntu.com/DebuggingProcedures. > > At a minimum, we need: > > 1. The specific steps or actions you took that caused you to encounter the > problem. > 2. The behavior you expected. > 3. The behavior you actually encountered (in as much detail as possible). > > Bug reporting is mostly about finding & fixing problems thus preventing > future users from hitting the same bug. > > I suspect a Support site would be more appropriate, eg. > https://answers.launchpad.net/ubuntu. You can also find help with your > problem in the support forum of your local Ubuntu community > http://loco.ubuntu.com/ or asking at https://askubuntu.com or > https://ubuntuforums.org, or for more support options please look at > https://discourse.ubuntu.com/t/community-support/709 > > You mention `grub` which is a boot loader; thus it's a boot issue and > the OS doesn't start? Screen blanking can occur during the boot process > (video hardware switches modes) for some hardware setups. Grub config > has documentation; eg. https://help.ubuntu.com/community/Grub2/Setup but > it's all geared at altering the boot process; or making the grub menu > more appealing. > > You're also not using Ubuntu kernel, with various 3rd party packages, > such as what is found in a 3rd OS/source (eg. not > `21.0.3-0ubuntu0.3~20.04.5` but > `21.2.2-1ubuntu1pop0~1634226723~20.04~b715ae2~dev` so issues should be > addressed with the 3rd party packager (possibly system76) as you're not > using Ubuntu packages. > > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1956263 > > Title: > Situationm > > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > I have been using ubuntu for nearly ten years, but have only recently > started taking things seriously. My particular issue is that every > now and then I have a screen blinking problem. I have done a bunch of > research, and it points to the grub configuration. I have downloaded > and installed grub customizer. But I am not sure what all the options > are and am afraid of messing anyting up. Not sure that coming here > will help, or how I can pay for any help. Thanks for reading, and for > any help you are able to provide. PS I am running Ubundu 20.03 on a > System 76 Mini box. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > Uname: Linux 5.15.5-76051505-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu27.21 > Architecture: amd64 > BootLog: > > CasperMD5CheckResult: skip > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > Date: Mon Jan 3 18:28:39 2022 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: I just need to know a workaround > GraphicsCard: >Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if > 00 [VGA controller]) > Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS > 802.11n WLAN Adapter >Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver >Bus 001 Device 004: ID 8087:0aaa Intel Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: System76 Meerkat > ProcEnviron: >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.5-76051505-generic > root=UUID=bcaa96a9-3ebb-4f61-8b4d-bf8382de31aa ro > Renderer: Software > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/28/2018 > dmi.bios.release: 5.6 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: BECFL357.86A.0056.2018.1128.1717 > dmi.board.name: NUC8BEB > dmi.board.vendor: Intel Corporation > dmi.board.version: J72693-304 > dmi.chassis.type: 3 > dmi.chassis.vendor: System76 > dmi.chassis.version: meer4 > dmi.ec.firmware.release: 3.20 > dmi.m
[Bug 1956263] [NEW] Situationm
Public bug reported: I have been using ubuntu for nearly ten years, but have only recently started taking things seriously. My particular issue is that every now and then I have a screen blinking problem. I have done a bunch of research, and it points to the grub configuration. I have downloaded and installed grub customizer. But I am not sure what all the options are and am afraid of messing anyting up. Not sure that coming here will help, or how I can pay for any help. Thanks for reading, and for any help you are able to provide. PS I am running Ubundu 20.03 on a System 76 Mini box. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.15.5-76051505-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 3 18:28:39 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Meerkat ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.5-76051505-generic root=UUID=bcaa96a9-3ebb-4f61-8b4d-bf8382de31aa ro Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2018 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0056.2018.1128.1717 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: meer4 dmi.ec.firmware.release: 3.20 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0056.2018.1128.1717:bd11/28/2018:br5.6:efr3.20:svnSystem76:pnMeerkat:pvrmeer4:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnSystem76:ct3:cvrmeer4:skuBOXNUC8i3BEK: dmi.product.family: Intel NUC dmi.product.name: Meerkat dmi.product.sku: BOXNUC8i3BEK dmi.product.version: meer4 dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1pop0~1634226451~20.04~d7878ab~dev version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1pop0~1634226723~20.04~b715ae2~dev version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1pop0~1634226723~20.04~b715ae2~dev version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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: Tue Dec 17 17:36:58 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956263 Title: Situationm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950089] [NEW] package gir1.2-signon-2.0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-si
Public bug reported: (synaptic:6993): Gtk-CRITICAL **: 08:37:31.489: ../../../../gtk/gtktreeview.c:5602 (gtk_tree_view_bin_draw): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. (synaptic:6993): Gtk-CRITICAL **: 08:37:33.262: ../../../../gtk/gtktreeview.c:5602 (gtk_tree_view_bin_draw): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. Trying to upgrade from 21.04 to 21.10 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: gir1.2-signon-2.0 (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Nov 7 08:31:03 2021 DuplicateSignature: package:gir1.2-signon-2.0:(not installed) Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-cZZliD/035-gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 ErrorMessage: trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 InstallationDate: Installed on 2017-04-05 (1676 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: libsignon-glib Title: package gir1.2-signon-2.0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libsignon-glib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950089 Title: package gir1.2-signon-2.0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist- packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1950089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946660] Re: Ubuntu port of v4l2loopback doesn't behave the same as official port (v0.12.5)
This bug affects me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946660 Title: Ubuntu port of v4l2loopback doesn't behave the same as official port (v0.12.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1946660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946521] [NEW] motion fails to start after install: Permission denied creating log file
Public bug reported: I installed motion for the first time on a reasonably fresh Kubuntu 21.04 release. I installed this system in April 2021. It immediately fails and spams "emergency" log messages all over my terminals. (See dpkg log below) The problem seems to be that the default config /etc/motion/motion.conf specifies: log_file /var/log/motion/motion.log but there is nothing to create that directory. I'm not sure whether this should be a job for postinst, or a systemd ExecStartPre, but I would argue that not logging to a file at all and letting systemd-journald hoover up the stderr/syslog messages would be better. Indeed, if I remove the log_file line from /etc/motion/motion.conf, motion starts and runs perfectly well, and I get log messages in systemctl status. Thanks, Bruce Dpkg log: Setting up motion (4.3.2-1) ... Adding group `motion' (GID 134) ... Done. Warning: The home dir /var/lib/motion you specified already exists. Adding system user `motion' (UID 127) ... Adding new user `motion' (UID 127) with group `motion' ... The home directory `/var/lib/motion' already exists. Not copying from `/etc/skel'. adduser: Warning: The home directory `/var/lib/motion' does not belong to the user you are currently creating. Adding user `motion' to group `video' ... Adding user motion to group video Done. Created symlink /etc/systemd/system/multi-user.target.wants/motion.service → /lib/systemd/system/motion.service. Processing triggers for man-db (2.9.4-2) ... Broadcast message from systemd-journald@w7700 (Fri 2021-10-08 01:05:54 BST): motion[1372993]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied ** Affects: motion (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/1946521 Title: motion fails to start after install: Permission denied creating log file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/motion/+bug/1946521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945360] Re: grub did not install
Drive was "no OS" and apparently the partition table was ms-dos, Wiped and created a new partition tab;e. Maybe loader should detect incompatible tables. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945360 Title: grub did not install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1945360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945360] [NEW] grub did not install
Public bug reported: Fresh install with manual partitions. Tried several times using sda, sda7, sda1 Kubuntu 20.04.1. Before last try I did apt update & upgrade. SO. now Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445.1 CurrentDesktop: KDE Date: Tue Sep 28 14:34:27 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kubuntu ubiquity-20.04.15.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945360 Title: grub did not install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1945360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Forgot to mention this problem also exists in hirsute with 5.11.0-7620-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I just want to share a quick observation related to this bug. I've noticed that when there is a kernel update and doing a soft-reboot, this problem shows up. When this occurs, I do a soft-shutdown and power up and the problem is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908656] Re: Evolution renders email attachments for a long time
I'm seeing a similar problem occurring in Ubuntu 18.04 with Evolution 3.28.5-0ubuntu0.18.04.2 with a new e-mail being composed and attaching or detaching a local file with a size of 65KB which hangs Evolution for about 20-30 seconds. This problem did not occur on a previous versions of Evolution. Additionally this is running on LTSP Fat Clients via SSH home mounts. I'm not sure if my issue and this issue is related. Let me know if I need to submit a new bug report instead. Happy to provide any debugging information as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908656 Title: Evolution renders email attachments for a long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1908656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927245] [NEW] attempting to upgrade to 20.04
Public bug reported: Ubuntu 18.04 to 20.04 Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed May 5 11:40:28 2021 InstallationDate: Installed on 2013-12-17 (2696 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-05-05 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927245 Title: attempting to upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922501] [NEW] Failure to format SSD disk during install
Public bug reported: See log ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 4 20:04:27 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922501 Title: Failure to format SSD disk during install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913857] [NEW] Installer crashes after removing RAID Controller
Public bug reported: LSI MegaRAID SAS9260-8i Card. Also corrupted separate install on SSD requiring another install. This is the one that crashed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 22:51:19 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913857 Title: Installer crashes after removing RAID Controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1913857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913791] [NEW] Install fail on SSD Drive residing on LSI 9260-8i RAID Controller configured as RAID 0 VD6
Public bug reported: LSI MegaRAID SAS 9260-8i RAID Controller 7 - 2.5" SSD Drive GIGABYTE A320M-A2SH MB AMD A8-9600 CPU 16GB DD4-3200 RAM 8-drive backplane. address: (252) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 13:24:59 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913791 Title: Install fail on SSD Drive residing on LSI 9260-8i RAID Controller configured as RAID 0 VD6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1913791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
Ok thank you, I can confirm then that lp1909005 is definitely installed but still not waking from sleep corfectly. If it is any help...one difference I have noticed between working 5.4.0-26 and later non-working versions (including lp1909005 but previous ones too): with -26 the login (SDDM) screen is displayed, then the screen goes blank for half a second before it is redisplayed, and the same for the desktop - it is displayed, then the screen goes blank, then it is redisplayed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
Still no change in symptoms I'm afraid. PS I tried uname -r after installing and it printed the same as normal 5.4.0-59...is that what you would expect? (Just trying to verify that lp1909005 is running, but it appeared to do all the right sort of things when I was installing it, but I have not installed a non-standard kernel before) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
Sorry to have to report that 5.4.0-59.65 does not fix it for me, symptoms unchanged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906741] Re: Firefox sometimes causes garbled audio
This happens to me also. Weirdly, only Twitter videos seem affected. It's possible it happens elsewhere, but I haven't seen it yet. Ubuntu 20.10 Firefox 84 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906741 Title: Firefox sometimes causes garbled audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1906741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
In my case I had a new Dell 17 3793, updated BIOS, and installed Kubuntu 20.04 from a USB stick I created at the time 20.04 was released. If I don't give the install program access to the internet, then wake from suspend suspend works. But if I do give the install program access to the internet, or if I sudo apt update && sudo apt upgrade after install, then wake from suspend doesn't work. Using the original 20.04 kernel, 5.4.0-26 works but no later kernels I have tried work. Further observations on failed wakeup: blank screen with flashing cursor. Caps Lock light does not change. But PrtScr+Ctrl+Alt+REISUB reboots. Ctrl+Alt+F2 or F3 etc and the cursor gives a barely observable flicker. Ctrl+Alt+F1 which should bring up the graphical login screen causes the flashing cursor to disappear, but still blank screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903483] [NEW] "Caps Lock is also a Ctrl" setting stops working when connecting an external keyboard
Public bug reported: In Tweaks, I've set the "Caps Lock is also a Ctrl" setting. However, when I connect my external keyboard via USB, the setting stops taking effect. If I go to Tweaks, the setting still appears to be enabled, but I have to disable it and re-enable it to make it take effect again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mgummelt 2175 F pulseaudio /dev/snd/pcmC1D7p: mgummelt 2175 F...m pulseaudio /dev/snd/controlC0: mgummelt 2175 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 21:15:48 2020 HibernationDevice: RESUME=UUID=b92322bb-a24e-4286-8452-f6e2272a4fb3 InstallationDate: Installed on 2018-03-26 (959 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20ENCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=ab4a36d6-e419-424e-9f0d-3635cd2543b5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-09 (122 days ago) WifiSyslog: dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET86W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20ENCTO1WW dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903483 Title: "Caps Lock is also a Ctrl" setting stops working when connecting an external keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902172] [NEW] printer failure
Public bug reported:
Page 1 ():
{'cups_connection_failure': False}
Page 2 ():
{'local_server_exporting_printers': False}
Page 3 ():
{'cups_dests_available': [], 'cups_queue_listed': False}
Page 4 ():
{'printer_is_remote': False}
Page 5 ():
{'cups_device_listed': False, 'cups_devices_available': {}}
Page 6 ():
{'printer_page_size': None,
'system_locale_lang': None,
'user_locale_ctype': 'en_AU',
'user_locale_messages': 'en_AU'}
** 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/1902172
Title:
printer failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1902172/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902171] [NEW] /usr/games/kpat
Public bug reported: === Info === PID: 5537 (kpat) UID: 1000 (b) GID: 1000 (b) Signal: 11 (SEGV) Timestamp: Wed 2020-10-28 19:52:20 AEDT (1 day 20h ago) Command Line: kpat -qwindowtitle KPatience Executable: /usr/games/kpat Control Group: /user.slice/user-1000.slice/session-c1.scope Unit: session-c1.scope Slice: user-1000.slice Session: c1 Owner UID: 1000 (b) Boot ID: 7989c185d2734127a2b722b3109b4e6e Machine ID: b76cc7b1bbdc489e93909d2043031de8 Hostname: b-System-Product-Name Storage: /var/lib/systemd/coredump/core.kpat.1000.7989c185d2734127a2b722b3109b4e6e.5537.1603875140.lz4 Message: Process 5537 (kpat) of user 1000 dumped core. Stack trace of thread 5537: #0 0x7f335dbf35a0 _ZNK16KSharedDataCache4findERK7QStringP10QByteArray (libKF5CoreAddons.so.5 + 0x745a0) #1 0x7f335e0107f5 n/a (libkcardgame.so + 0x1a7f5) #2 0x7f335c9d8d5a _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b2d5a) #3 0x7f335d498a66 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16aa66) #4 0x7f335d4a20f0 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1740f0) #5 0x7f335c9ac93a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28693a) #6 0x7f335c9af5b8 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2895b8) #7 0x7f335ca04f67 n/a (libQt5Core.so.5 + 0x2def67) #8 0x7f335a662fbd g_main_context_dispatch (libglib-2.0.so.0 + 0x51fbd) #9 0x7f335a663240 n/a (libglib-2.0.so.0 + 0x52240) #10 0x7f335a6632e3 g_main_context_iteration (libglib-2.0.so.0 + 0x522e3) #11 0x7f335ca04565 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2de565) #12 0x7f335c9ab4db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2854db) #13 0x7f335c9b3246 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x28d246) #14 0x560be3efce3a n/a (kpat + 0x27e3a) #15 0x7f335c22b0b3 __libc_start_main (libc.so.6 + 0x270b3) #16 0x560be3efdaee n/a (kpat + 0x28aee) Stack trace of thread 5543: #0 0x7f335aece376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f334edfe62b n/a (iris_dri.so + 0x47c62b) #2 0x7f334edfe23b n/a (iris_dri.so + 0x47c23b) #3 0x7f335aec7609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f335c326293 __clone (libc.so.6 + 0x122293) Stack trace of thread 5540: #0 0x7f335c319aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f335a206c1a n/a (libxcb.so.1 + 0xbc1a) #2 0x7f335a20890a xcb_wait_for_event (libxcb.so.1 + 0xd90a) #3 0x7f335798f298 n/a (libQt5XcbQpa.so.5 + 0x78298) #4 0x7f335c7e49d2 n/a (libQt5Core.so.5 + 0xbe9d2) #5 0x7f335aec7609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f335c326293 __clone (libc.so.6 + 0x122293) Stack trace of thread 5544: #0 0x7f335aece376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f334edfe62b n/a (iris_dri.so + 0x47c62b) #2 0x7f334edfe23b n/a (iris_dri.so + 0x47c23b) #3 0x7f335aec7609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f335c326293 __clone (libc.so.6 + 0x122293) Stack trace of thread 5541: #0 0x7f335c319aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f335a6631ae n/a (libglib-2.0.so.0 + 0x521ae) #2 0x7f335a6632e3 g_main_context_iteration (libglib-2.0.so.0 + 0x522e3) #3 0x7f335ca04565 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2de565) #4 0x7f335c9ab4db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2854db) #5 0x7f335c7e3785 _ZN7QThread4execEv (libQt5Core.so.5 + 0xbd785) #6 0x7f335b169efa n/a (libQt5DBus.so.5 + 0x17efa) #7 0x7f335c7e49d2 n/a (libQt5Core.so.5 + 0xbe9d2)
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I'd like to add that I'm seeing this with Groovy as well: Oct 26 19:08:40 ubuntu kernel: [ cut here ] Oct 26 19:08:40 ubuntu kernel: NETDEV WATCHDOG: enp3s0 (r8169): transmit queue 0 timed out Oct 26 19:08:40 ubuntu kernel: WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x25b/0x270 Oct 26 19:08:40 ubuntu kernel: Modules linked in: cfg80211 8021q garp mrp stp llc nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic intel_rapl_msr mei_hdcp ledtrig_audio snd_hda_codec_hdmi snd_hda_intel in> Oct 26 19:08:40 ubuntu kernel: hid_generic usbhid hid uas usb_storage amdgpu iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_inte> Oct 26 19:08:40 ubuntu kernel: CPU: 6 PID: 0 Comm: swapper/6 Tainted: G OE 5.8.0-7625-generic #26~1603126178~20.10~210fe73-Ubuntu Oct 26 19:08:40 ubuntu kernel: Hardware name: MSI MS-7850/H97 PC Mate(MS-7850), BIOS V5.9 02/16/2016 Oct 26 19:08:40 ubuntu kernel: RIP: 0010:dev_watchdog+0x25b/0x270 Oct 26 19:08:40 ubuntu kernel: Code: 85 c0 75 e5 eb 9c 4c 89 ff c6 05 26 85 1c 01 01 e8 2a 93 fa ff 44 89 e9 4c 89 fe 48 c7 c7 c0 7a a8 b1 48 89 c2 e8 ba 30 64 ff <0f> 0b e9 7a ff ff ff 66 66 2e 0f 1f 84 00 00 00 > Oct 26 19:08:40 ubuntu kernel: RSP: 0018:ad1500210e78 EFLAGS: 00010286 Oct 26 19:08:40 ubuntu kernel: RAX: RBX: 9b0179912200 RCX: 9b018dd98cd8 Oct 26 19:08:40 ubuntu kernel: RDX: ffd8 RSI: 0027 RDI: 9b018dd98cd0 Oct 26 19:08:40 ubuntu kernel: RBP: ad1500210ea8 R08: 0004 R09: 047a Oct 26 19:08:40 ubuntu kernel: R10: R11: 0001 R12: 9b0179912280 Oct 26 19:08:40 ubuntu kernel: R13: R14: 9b01788da480 R15: 9b01788da000 Oct 26 19:08:40 ubuntu kernel: FS: () GS:9b018dd8() knlGS: Oct 26 19:08:40 ubuntu kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 26 19:08:40 ubuntu kernel: CR2: 7f7677e18c90 CR3: a5c0a005 CR4: 001606e0 Oct 26 19:08:40 ubuntu kernel: Call Trace: Oct 26 19:08:40 ubuntu kernel: Oct 26 19:08:40 ubuntu kernel: ? pfifo_fast_enqueue+0x150/0x150 Oct 26 19:08:40 ubuntu kernel: call_timer_fn+0x32/0x130 Oct 26 19:08:40 ubuntu kernel: __run_timers.part.0+0x184/0x280 Oct 26 19:08:40 ubuntu kernel: ? lapic_next_deadline+0x26/0x30 Oct 26 19:08:40 ubuntu kernel: ? clockevents_program_event+0x8f/0xe0 Oct 26 19:08:40 ubuntu kernel: run_timer_softirq+0x2a/0x50 Oct 26 19:08:40 ubuntu kernel: __do_softirq+0xd0/0x2a1 Oct 26 19:08:40 ubuntu kernel: asm_call_irq_on_stack+0x12/0x20 Oct 26 19:08:40 ubuntu kernel: Oct 26 19:08:40 ubuntu kernel: do_softirq_own_stack+0x3d/0x50 Oct 26 19:08:40 ubuntu kernel: irq_exit_rcu+0x95/0xd0 Oct 26 19:08:40 ubuntu kernel: sysvec_apic_timer_interrupt+0x3b/0x90 Oct 26 19:08:40 ubuntu kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Oct 26 19:08:40 ubuntu kernel: RIP: 0010:cpuidle_enter_state+0xb7/0x3f0 Oct 26 19:08:40 ubuntu kernel: Code: 3f fb 06 4f e8 4a 5d 74 ff 48 89 45 d0 0f 1f 44 00 00 31 ff e8 fa 68 74 ff 80 7d c7 00 0f 85 d3 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 df 01 00 00 49 63 d4 48 8d 04 52 > Oct 26 19:08:40 ubuntu kernel: RSP: 0018:ad15000c7e48 EFLAGS: 0246 Oct 26 19:08:40 ubuntu kernel: RAX: 9b018ddac6c0 RBX: 9b018ddb7900 RCX: 001f Oct 26 19:08:40 ubuntu kernel: RDX: RSI: 229f RDI: Oct 26 19:08:40 ubuntu kernel: RBP: ad15000c7e88 R08: 000aae6ba9e9 R09: Oct 26 19:08:40 ubuntu kernel: R10: 011b R11: 9b018ddab364 R12: 0005 Oct 26 19:08:40 ubuntu kernel: R13: b216adc0 R14: 0005 R15: Oct 26 19:08:40 ubuntu kernel: ? cpuidle_enter_state+0xa6/0x3f0 Oct 26 19:08:40 ubuntu kernel: cpuidle_enter+0x2e/0x40 Oct 26 19:08:40 ubuntu kernel: cpuidle_idle_call+0x145/0x200 Oct 26 19:08:40 ubuntu kernel: do_idle+0x7a/0xe0 Oct 26 19:08:40 ubuntu kernel: cpu_startup_entry+0x20/0x30 Oct 26 19:08:40 ubuntu kernel: start_secondary+0xe6/0x100 Oct 26 19:08:40 ubuntu kernel: secondary_startup_64+0xb6/0xc0 Oct 26 19:08:40 ubuntu kernel: ---[ end trace ef40ba07e8939a6f ]--- Oct 26 19:08:40 ubuntu kernel: r8169 :03:00.0 enp3s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). I'm currently running 5.4.0-7642.46~1598628707~20.04~040157c (Pop_OS!) to mitigate this issue, but it's currently present in 5.8.0-7625.26~1603126178~20.10~210fe73. Same symptoms as the original reporter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464
[Bug 1896853] [NEW] package linux-headers-5.4.0-48 5.4.0-48.52 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-5.4.0-48.list-new': Operation not permitted
Public bug reported: occurred while patching was taking place ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-48 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bhbruce1696 F pulseaudio /dev/snd/controlC1: bhbruce1696 F pulseaudio CasperMD5CheckResult: skip Date: Wed Sep 23 19:37:59 2020 DuplicateSignature: package:linux-headers-5.4.0-48:5.4.0-48.52 Unpacking linux-modules-extra-5.4.0-48-generic (5.4.0-48.52) ... dpkg: error processing archive /tmp/apt-dpkg-install-0r4drJ/05-linux-modules-extra-5.4.0-48-generic_5.4.0-48.52_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.4.0-48-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-headers-5.4.0-48.list-new': Operation not permitted InstallationDate: Installed on 2020-08-09 (45 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20378 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=bafcf03f-eca8-4d34-b66d-d181b3c3314a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 SourcePackage: linux Title: package linux-headers-5.4.0-48 5.4.0-48.52 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-5.4.0-48.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN37WW(V2.01) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN37WW(V2.01):bd02/11/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.sku: LENOVO_MT_20378_BU_idea_FM_Lenovo Y50-70 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896853 Title: package linux-headers-5.4.0-48 5.4.0-48.52 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-5.4.0-48 .list-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890382] Re: Gnome-terminal maximize loses one line of terminal output
Attaching original screenshots: gnomeTerminalMaximiseBugScreenshot1-afterLScommand.png gnomeTerminalMaximiseBugScreenshot2-afterMaximize.png ** Attachment added: "gnomeTerminalMaximiseBugScreenshots.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5399148/+files/gnomeTerminalMaximiseBugScreenshots.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890382 Title: Gnome-terminal maximize loses one line of terminal output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890382] Re: Gnome-terminal maximize loses one line of terminal output
I have encountered a seemingly related issue where ls is sometimes displaying different output depending on the terminal display size (and when the function is called), independent of maximisation. ** Attachment added: "gnomeTerminalDisplayBugScreenshot.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5399141/+files/gnomeTerminalDisplayBugScreenshot.png ** Attachment removed: "gnomeTerminalMaximiseBugScreenshots.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5398803/+files/gnomeTerminalMaximiseBugScreenshots.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890382 Title: Gnome-terminal maximize loses one line of terminal output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890382] [NEW] Gnome-terminal maximize loses one line of terminal output
Public bug reported: Gnome-terminal maximize loses one line of terminal output. Summary: 1. Assume the gnome-terminal currently contains output that exceeds the maximum number of characters of its current display area (ie the text is wrapped) 2. Maximise the gnome-terminal 3. Note that one line of the original content is lost Replication: cd ~/gnomeTerminalBug/replicationTest touch 01.txt touch 02.txt touch 03.txt touch 04.txt touch 05.txt touch 06.txt touch 07.txt touch 08.txt touch 09.txt touch 10.txt touch 11.txt touch 12.txt touch 13.txt touch 14.txt touch 15.txt touch 16.txt touch 17.txt touch 18.txt touch 19.txt touch 20.txt touch 21.txt touch 22.txt touch 23.txt touch 24.txt touch 25.txt touch 26.txt touch 27.txt touch 28.txt touch 29.txt touch 30.txt touch 31.txt touch 32.txt touch 33.txt touch 34.txt touch 35.txt touch 36.txt touch 37.txt touch 38.txt touch 39.txt touch 40.txt touch 41.txt touch 42.txt touch 43.txt touch 44.txt touch 45.txt touch 46.txt touch 47.txt touch 48.txt touch 49.txt touch 50.txt touch 51.txt touch 000
[Bug 1888138] [NEW] Selecting "Show Hidden Files" hides desktop icons randomly
Public bug reported: Ubuntu 20.4 LTS Nautilus 3.36.3 What I expect to happen: When selecting "Show Hidden Files" checkbox, I expect any icons on my desktop for hidden files to appear and for icons for regular files to remain visible. What actually happens: when I select the "Show Hidden Files" checkbox, random icons on my desktop are hidden. When deselecting the same checkbox, sometimes not all the missing icons reappear. There appears to be no pattern to the missing icons. Different icons are hidden on different occasions and there is no consistency as to the file type hidden (sometimes one icon for a .txt file is hidden and another icon for a different .txt file is not, for example). When navigating to the Desktop folder in Nautilus the expected behavior is observed - i.e hidden file visibility is toggled in the Nautilus window, regular files remain listed always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 16:43:36 2020 InstallationDate: Installed on 2017-01-26 (1269 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-07-17 (1 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888138 Title: Selecting "Show Hidden Files" hides desktop icons randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1888138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887559] [NEW] Attempt to upgrade 16.04 to 18.04 via terminal
Public bug reported: Here is the terminal session that failed video1@video1-Latitude-E6510:~$ sudo apt update [sudo] password for video1: Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB] Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB] Hit:4 http://ppa.launchpad.net/stefansundin/truecrypt/ubuntu xenial InRelease Get:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB] Hit:6 http://ppa.launchpad.net/unit193/encryption/ubuntu xenial InRelease Fetched 325 kB in 0s (368 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. video1@video1-Latitude-E6510:~$ apt upgrade E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? video1@video1-Latitude-E6510:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: gstreamer1.0-plugins-good : Depends: libgstreamer-plugins-good1.0-0 (= 1.8.3-1ubuntu0.4) but 1.14.2-1ubuntu3 is installed libgstreamer-plugins-good1.0-0 : Depends: libgstreamer-plugins-base1.0-0 (>= 1.14.2) but 1.8.3-1ubuntu0.3 is installed Depends: libgstreamer1.0-0 (>= 1.14.2) but 1.8.3-1~ubuntu0.1 is installed E: Unmet dependencies. Try using -f. video1@video1-Latitude-E6510:~$ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: gstreamer1.0-plugins-good : Depends: libgstreamer-plugins-good1.0-0 (= 1.8.3-1ubuntu0.4) but 1.14.2-1ubuntu3 is installed libgstreamer-plugins-good1.0-0 : Depends: libgstreamer-plugins-base1.0-0 (>= 1.14.2) but 1.8.3-1ubuntu0.3 is installed Depends: libgstreamer1.0-0 (>= 1.14.2) but 1.8.3-1~ubuntu0.1 is installed E: Unmet dependencies. Try using -f. video1@video1-Latitude-E6510:~$ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: gstreamer1.0-plugins-good : Depends: libgstreamer-plugins-good1.0-0 (= 1.8.3-1ubuntu0.4) but 1.14.2-1ubuntu3 is installed libgstreamer-plugins-good1.0-0 : Depends: libgstreamer-plugins-base1.0-0 (>= 1.14.2) but 1.8.3-1ubuntu0.3 is installed Depends: libgstreamer1.0-0 (>= 1.14.2) but 1.8.3-1~ubuntu0.1 is installed E: Unmet dependencies. Try using -f. video1@video1-Latitude-E6510:~$ sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: gstreamer1.0-plugins-good : Depends: libgstreamer-plugins-good1.0-0 (= 1.8.3-1ubuntu0.4) but 1.14.2-1ubuntu3 is installed libgstreamer-plugins-good1.0-0 : Depends: libgstreamer-plugins-base1.0-0 (>= 1.14.2) but 1.8.3-1ubuntu0.3 is installed Depends: libgstreamer1.0-0 (>= 1.14.2) but 1.8.3-1~ubuntu0.1 is installed E: Unmet dependencies. Try using -f. video1@video1-Latitude-E6510:~$ ^C video1@video1-Latitude-E6510:~$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... failed. The following packages have unmet dependencies: gstreamer1.0-plugins-good : Depends: libgstreamer-plugins-good1.0-0 (= 1.8.3-1ubuntu0.4) but 1.14.2-1ubuntu3 is installed libgstreamer-plugins-good1.0-0 : Depends: libgstreamer-plugins-base1.0-0 (>= 1.14.2) but 1.8.3-1ubuntu0.3 is installed Depends: libgstreamer1.0-0 (>= 1.14.2) but 1.8.3-1~ubuntu0.1 is installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Unable to correct dependencies video1@video1-Latitude-E6510:~$ sudo apt install update-manager-core Reading package lists... Done Building dependency tree Reading state information... Done update-manager-core is already the newest version (1:16.04.17). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: gstreamer1.0-plugins-good : Depends: libgstreamer-plugins-good1.0-0 (= 1.8.3-1ubuntu0.4) but 1.14.2-1ubuntu3 is to be installed libgstreamer-plugins-good1.0-0 : Depends: libgstreamer-plugins-base1.0-0 (>= 1.14.2) but 1.8.3-1ubuntu0.3 is to be installed Depends: libgstreamer1.0-0 (>= 1.14.2) but
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Running 20.04. Seems to me this bug appears only after I run Transmission Bit Torrent Client. My log files have shown that my kernel has been changed and after that I may lose wifi and lan connectivity. I have performed a fresh install of 20.04 numerous times to eliminate the problem and have run a fresh install for days without any problems until Transmission is run. Logs show that the my kernel was modified from root however I do not even know how to access root much less make changes to the kernel. I am wondering if there is some agency or entity that makes these changes as root to prevent torrenting, Below is copy of my warnings from logs. 10:12:38 PM dbus-daemon: [session uid=1000 pid=1610] Successfully activated service 'org.gnome.Logs' 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). 9:07:50 PM systemd: tracker-store.service: Succeeded. 9:07:50 PM tracker-store: OK 9:07:20 PM systemd: Started Tracker metadata database store and lookup manager. 9:07:20 PM dbus-daemon: [session uid=1000 pid=1610] Successfully activated service 'org.freedesktop.Tracker1' 9:07:20 PM systemd: Starting Tracker metadata database store and lookup manager... 9:07:20 PM dbus-daemon: [session uid=1000 pid=1610] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.0' (uid=1000 pid=1607 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Below is copy of my logs with "kernel" in the search option. 8:42:53 PM kernel: perf: interrupt took too long (3942 > 3930), lowering kernel.perf_event_max_sample_rate to 50500 6:59:33 PM kernel: snd_hda_codec_idt hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) 6:59:33 PM kernel: [TTM] Zone kernel: Available graphics memory: 1746504 KiB 6:59:33 PM kernel: [drm] initializing kernel modesetting (SUMO 0x1002:0x9647 0x103C:0x169B 0x00). 6:59:27 PM kernel: Started udev Kernel Device Manager. 6:59:27 PM kernel: Starting udev Kernel Device Manager... 6:59:27 PM kernel: Finished Apply Kernel Variables. 6:59:27 PM kernel: Mounted Kernel Configuration File System. 6:59:27 PM kernel: Starting Apply Kernel Variables... 6:59:27 PM kernel: Mounting Kernel Configuration File System... 6:59:27 PM kernel: Finished Load Kernel Modules. 6:59:27 PM kernel: Mounted Kernel Trace File System. 6:59:27 PM kernel: Starting Remount Root and Kernel File Systems... 6:59:27 PM kernel: Mounting Kernel Trace File System... 6:59:27 PM kernel: Listening on udev Kernel Socket. 6:59:27 PM kernel: Freeing unused kernel image memory: 1192K 6:59:27 PM kernel: Write protecting the kernel read-only data: 22528k 6:59:27 PM kernel: Freeing unused kernel image memory: 2712K 6:59:27 PM kernel: Loaded X.509 cert 'Build time autogenerated kernel key: fc5d997396576c92a1f0014cbc11f394a5a98020' 6:59:27 PM kernel: Memory: 3432580K/3648416K available (14339K kernel code, 2397K rwdata, 4952K rodata, 2712K init, 4992K bss, 215836K reserved, 0K cma-reserved) 6:59:27 PM kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 6:59:27 PM kernel: Booting paravirtualized kernel on bare hardware 6:59:27 PM kernel: KERNEL supported cpus: This log show no unusual changes as noted from previous sessions requiring a fresh install with the possible exception of the first line of the above log, but I included it for reference. Has anybody else noticed these warnings after torrenting? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shel
[Bug 1874066] Re: Cannot install on non-RST drive if RST is enabled and there is a second RST-enabled drive
Can I jump on this bug? My laptop's a MSI Titan. From the factory, they RAID together two 500GB SSD drives with a windows 10 install. There's also a 1TB 7200 RPM SATA disk which I'd installed Ubuntu 18.04 in the past with no problems. I know that 20.04 will run on this machine and if the installer would simply provide a way to continue the install despite the fact that RST is detected on the machine, I could just install it. Just make it a warning, possibly even a very strong warning, but provide a way to continue anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874066 Title: Cannot install on non-RST drive if RST is enabled and there is a second RST-enabled drive To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1874066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Command to reproduce the issue: echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | grep vmovaps The expected output is that the objdump output matches the vmovaps instruction input. When using binutils with the bug, the initial 0x40 will be incorrect. >From an Ubuntu 20.04 system: $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | grep vmovaps 0: 62 f1 7c 48 28 04 05vmovaps 0x40(,%rax,1),%zmm0 On an Ubuntu 18.04 system: $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | grep vmovaps 0: 62 f1 7c 48 28 04 05vmovaps 0x1(,%rax,1),%zmm0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882527] Re: mysql timeoutsec results in killing mysql process
Thanks Daniel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882527 Title: mysql timeoutsec results in killing mysql process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1882527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882527] Re: mysql timeoutsec results in killing mysql process
I see I have created this bug report in xorg instead of MySQL. Please accept my apology and either move or delete. I am happy to recreate, just tell me which. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882527 Title: mysql timeoutsec results in killing mysql process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882527] [NEW] mysql timeoutsec results in killing mysql process
Public bug reported: MySQL on 20.04 has TimeoutSec set to 600 (IIRC) in the systemd script. This has the effect of killing the MySQL process if this timeout is reached. IMHO this is a Very Bad Idea. A database server process should only be force killed by a user action. I would prefer that the server had unlimited time to cleanly shutdown and startup (eg if recovering). Our DB is about 500GB with some very large tables (for us at least) eg. 250GB and we've had more than a few unfortunate delays as a result of delayed startup caused by recoveries because MySQL was killed prematurely. Because MySQL 8.0 has reduced the default logging level, it was not clear to me that the process was being force killed. I believe the MySQL team are of the same view as me per https://bugs.mysql.com/bug.php?id=91423: ``` [12 Jul 2019 15:57] Paul Dubois Posted by developer: Fixed in 8.0.18. On Debian, long InnoDB recovery times at startup could cause systemd service startup failure. The default systemd service timeout is now disabled (consistent with RHEL) to prevent this from happening. ``` ** Affects: xorg-server (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/1882527 Title: mysql timeoutsec results in killing mysql process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559331] Re: Permanent "Printer-out-of-paper" message.
I also have this problem on a Samsung ML-2855 ND remote shared printer on Ubuntu 18.04 server Using Ubuntu 20.04. When printing pdf file using lp or printing from Chrome browser the printer turns on paper out signal and cannot be cleared without turning off printer and turning back on again. Another printer, HP Photosmart works perfectly with lp and browser. Tried removing and reinstalling CUPS which found printer, but paper out bug still persists with printing from terminal. Seems a "paper out" signal is being sent which is a control character for the Samsung but not for the HP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/559331 Title: Permanent "Printer-out-of-paper" message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72531] Re: Merge editor horizontal scrollbar not working
The kdiff3 horizontal scrollbar is failing on Ubuntu 20.04. When the user moves the horizontal scrollbar the two panes are not refreshed with the new currently out of screen contents (only the existing contents are shown and scrolled through). What should be the new contents is shown as white space. After moving the horizontal scrollbar the user can click inside a pane for the contents to refresh (on both panes), but this workaround is both awkward and temperamental. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/72531 Title: Merge editor horizontal scrollbar not working To manage notifications about this bug go to: https://bugs.launchpad.net/kdiff3/+bug/72531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Nope, never mind gnome-tweaks. Removed Chromium snap and installed Google Chrome. Problem goes away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Harrumph: not impressed. Was working fine this morning, then an update landed me with the snap version. Back to gnome-tweaks... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849859] Re: smb printing fails
This bug seems to still be active in Ubuntu 20.4 The "AuthInfoRequired username,password" workarround did NOT work on my system, as when I restarted cups, it rewrote the printers.conf file without the password and user. However what did work for me was adding the printer and adding my credentials at the same time in the SMB printer box! The format that worked was username:password@host_computer/printername. In the dialog, it deletes the username and password on the smb: line but adds them in the password and username boxes and this time writes them in the file. This seems very strange to me but it works for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
I have a Dell XPS L501X with exactly the same problem. The fix above: > volume control -> configuration to Analog Stereo Duplex (unplugged) I the only thing that has worked for me. I've tried multiple other suggestions on other sites, include renaming .config/pulse folder then reboot, force-reload of alsa, removing the pulse-audio and alsa-base packages from the system, and reinstalling them, and reviewing all settings in alsa mixer. Ubuntu works perfectly on this laptop. I had 19.04 previously, and sound worked fine. An upgrade to 20.04 didn't work as selecting the nVidia video driver nvidia-driver-390 would not let the OS boot into the GUI. What is strange is a complete wipe and reinstall of 20.04 from scratch worked fine, and that video driver was selected automatically. I'm so glad I found this post, as I now have sound again. For now I'm content changing the setting by hand after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875454] Re: New ubuntu-20.04-preinstalled-server-arm64+raspi.img installed on R-Pi 4 does not boot if usercfg.txt is edited
** Package changed: ubuntu => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875454 Title: New ubuntu-20.04-preinstalled-server-arm64+raspi.img installed on R-Pi 4 does not boot if usercfg.txt is edited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1875454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875454] [NEW] New ubuntu-20.04-preinstalled-server-arm64+raspi.img installed on R-Pi 4 does not boot if usercfg.txt is edited
Public bug reported: 1. I installed this image on my R-Pi 4: ubuntu-20.04-preinstalled- server-arm64+raspi.img. It booted with no issues including SSH connection. 2. I then edited the boot/firmware/usercfg.txt and added dtoverlay=uart4 to allow access to an alternate UART. This has been working fine for me with 19.10.1 on the same hardware setup. 3. The RPi would not boot and nothing was sent out the serial console. 4. I placed the SD card back in my PC and removed the added line. Boot of the 20.04 image worked again. Release info: ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal Output of serial console with Stock 20.04 image(only password changed at initial boot) MMC: emmc2@7e34: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Net: No ethernet found. starting USB... No working controllers found ## Info: input data size = 6 = 0x6 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 2569 bytes read in 17 ms (147.5 KiB/s) ## Executing script at 0240 8377273 bytes read in 621 ms (12.9 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 29417535 bytes read in 2117 ms (13.3 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260e415 Starting kernel ... [0.940739] bcm2708_fb soc:fb: Unable to determine number of FB's. Assuming 1 [0.941825] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x8001 [0.941850] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) [0.941898] bcm2708_fb soc:fb: probe failed, err -22 [1.343885] spi-bcm2835 fe204000.spi: could not get clk: -517 ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory ext4 Thu Jan 1 00:00:05 UTC 1970 date: invalid date ' Wed Apr 1 17:23:43 2020' -.mount dev-mqueue.mount sys-kernel-debug.mount sys-kernel-tracing.mount kmod-static-nodes.service systemd-modules-load.service systemd-remount-fs.service ufw.service sys-fs-fuse-connections.mount sys-kernel-config.mount systemd-random-seed.service systemd-sysusers.service systemd-sysctl.service systemd-tmpfiles-setup-dev.service keyboard-setup.service lvm2-monitor.service systemd-udevd.service systemd-journald.service systemd-udev-trigger.service systemd-journal-flush.service [7.989412] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [8.249348] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [8.269839] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 systemd-rfkill.service systemd-udev-settle.service multipathd.service systemd-fsckd.service snap-core18-1708.mount snap-lxd-14808.mount snap-snapd-7267.mount systemd-fsck@dev-disk-by\x2dlabel-system\x2dboot.service boot-firmware.mount console-setup.service finalrd.service [ OK ] Finished Tell Plymouth To Write Out Runtime Data. [ OK ] Finished Create Volatile Files and Directories. systemd-tmpfiles-setup.service Starting Network Time Synchronization... Starting Update UTMP about System Boot/Shutdown... [ OK ] Finished Update UTMP about System Boot/Shutdown. systemd-update-utmp.service apparmor.service [ OK ] Finished Load AppArmor profiles. Starting Load AppArmor pro…managed internally by snapd... [ OK ] Finished Load AppArmor pro…s managed internally by snapd. snapd.apparmor.service [ OK ] Started Network Time Synchronization. systemd-timesyncd.service [ OK ] Reached target System Time Set. [ OK ] Reached target System Time Synchronized. [ 11.747964] cloud-init[1151]: Cloud-init v. 20.1-10-g71af48df-0ubuntu5 running 'init-local' at Sun, 26 Apr 2020 21:59:25 +. Up 11.30 seconds. [ OK ] Finished Initial cloud-init job (pre-networking). cloud-init-local.service [ OK ] Reached target Network (Pre). Starting Network Service... systemd-networkd.service [ OK ] Started Network Service. Starting Wait for Network to be Configured... Starting Network Name Resolution... [ OK ] Finished Wait for Network to be Configured. systemd-networkd-wait-online.service Starting Initial cloud-ini… (metadata service crawler)... [ OK ] Started Network Name Resolution. systemd-resolved.service [ OK ] Reached target Host and Network Name Lookups. [ 13.857611] cloud-init[1172]: Cloud-init v. 20.1-10-g71af48df-0ubuntu5 running 'init' at Sun, 26 Apr 2020 21:59:27 +. Up 13.44 seconds. [ 13.857972] cloud-init[1172]: ci-info:
[Bug 1797734] Re: slow calculator startup
This problem persists on Ubuntu 20.04. See this proposal to remove the snap version of the package: https://discourse.ubuntu.com/t/proposal- for-ubuntu-20-04lts/12969/92 Moreover, the apt package cannot currently be found on Ubuntu 20.04. Diagnosis: sudo snap remove gnome-calculator sudo apt-get install gnome-calculator Expected output: apt gnome-calculator successfully installed. Actual output: No apt package "gnome-calculator", but there is a snap with that name. Try "snap install gnome-calculator" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server
** Changed in: bind9 (Ubuntu) Status: New => Invalid ** Changed in: systemd (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/1862437 Title: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1862437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Last night I encountered similar bug behavior with a different message. Several hours after a printing related crash, another orphaned authentication dialog was painted on top of the gnome shell with the message: Please enter your password to access problem reports of system programs In light of this related problem and Sergey's suggestion of PAM involvement, I now believe the original bug in this thread is caused by incorrect handling of PAM by gnome shell. There could also be threading problems, insofar as the incorrect painting of an orphaned dialog window seems to occur long after the action that is referenced in the dialog window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server
My sincere apologies, I have been wasting your time ! The Ubuntu and derivatives distributions that use systemd-resolved do indeed query the assigned DNS. I verified this by stopping the DNSMASQ service, which resulted in the loss of external name resolution. Turning the service on again restored resolution of internet domain names. There is still an issue in distributions using systemd-resolved with resolution of LAN host names. As shown above resolution of a simple host name, in my examples BGOWIKI01v, fails. But when I add a 2nd name for that host to the /etc/hosts file on my DNSMASQ machine, with a suffix that looks like a domain name, like BGOWIKI01v.somedomain.local I can resolve the name correctly using the nslookup command. The solution for my reported issue will be to migrate my home LAN away an old-fashioned Workgroup model, to something that looks like a domain. Regards Bruce Goodman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862437 Title: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1862437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server
Apologies, I do not understand the interest in a vanilla lxc container. My test distributions are all default bare metal installations in a multi-boot configuration on a single ethernet connected laptop. My appreciation of the Test Case code above is that it is doing an nslookup on the host name of the querying machine - it is resolving its own name. The name resolution issue I'm trying to convey is that Ubuntu 16.10 and forward, and derivative distributions, do not query their assigned DNS to resolve host names of other devices on the LAN. In the example I have used, BGOWIKI01v resides on another of my LAN's computers. BGOWIKI01v has a static IP address asigned, as do several other servers and printers I have, and their IP address to hostname assignments are stored in the hosts file on my DNS server computer. So when my machines need to resolve a nearby host name it queries the DNS, which returns the address from its hosts file. That mechanism has been shown in the extracts provided above to work for the other cited distributions. Moreover, Windows (7 and 10) machines, tablets (both IOS and Android), and Android phones that connect wirelessly also resolve other host names on my LAN. Put simply, except for Ubuntu 16.10 forward and derivatives, the browsers on every other device on my LAN can resolve and load the wiki pages hosted on my BGOWIKI01v virtual. Ubuntu 16.10 forward and derivatives do not. This additional snippet may help - these commands were run on the Ubuntu 18.04 MATE petition; bruce@BGOLIN702:~$ nslookup BGOWIKI01v Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find BGOWIKI01v: SERVFAIL bruce@BGOLIN702:~$ nslookup > BGOWIKI01v Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find BGOWIKI01v: SERVFAIL > server 192.168.3.2 Default server: 192.168.3.2 Address: 192.168.3.2#53 > BGOWIKI01v Server: 192.168.3.2 Address: 192.168.3.2#53 Name:BGOWIKI01v Address: 192.168.3.60 > ^Cbruce@BGOLIN702:~$ nslookup BGOWIKI01v Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find BGOWIKI01v: SERVFAIL bruce@BGOLIN702:~ What this shows is name resolution fails, as I've described. But when I enter into nslookup and manually assign the DNS server the lookup succeeds. However, on exit from nslookup resolution again fails. Regards Bruce Goodman ** Changed in: bind9 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862437 Title: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1862437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Sergey, I think you might be onto something. I use a yubikey and have PAM configured to detect the yubikey automatically for sudo. So it could be a timing issue as you suggest, or maybe GNOME is making inappropriate assumptions about whether authentication requires actual user input. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
This morning, I managed to trigger this bug again. I installed a new component from the Activities/Search view. The component installed without requiring any authentication, but 30 minutes later, the offending authentication dialog image appeared on the screen. I believe there are probably two different bugs here: 1. In the ubuntu software install, there is probably a thread synchronization defect that allows software to install without authentication. 2. Separately gnome shell appears to paint widgets even though there is apparently no logic/process attached to the widget. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server
I have been aware of this bug for some time, so in preparation for filing the report I took a single laptop and did a default installation of each of the below listed distributions, then added their initial updates, then tested. On each distribution I ran this command; hostnamectl | grep System && hostnamectl | grep Kernel && nmcli dev show | grep DNS && nslookup BGOWIKI01v and after trimming out some clutter, combined the results into a single text file. It shows that each distribution acknowledges it has been assigned the DNS server (192.168.3.2) by the DHCP server, then it shows the success/failure of the nslookup command. As each distribution was installed specifically for this test, around the same time, and with default configurations, I cannot discern a local configuration problem. Rather, I think this test setup and results show conclusively that Ubuntu 16.04 correctly queries it's assigned DNS, while 18.04 & Pop!_OS 19.04 do not. Debian 10 (an upstream distribution) queries and resolves as expected, as do openSUSE Leap 15.1 and Fedora 31 Further, on 16.10 and derivatives, unless I add a local hosts file entry of; 192.168.3.60BGOWIKI01v browsers on those distributions cannot access the wiki running on BGOWIKI01v. The other named distributions do not need the hosts file entry as they resolve the name via the DNS as they should. "Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu" - please advise any further information needed ; I will keep the test laptop in tact for the life of this report. Regards Bruce Goodman ** Changed in: bind9 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862437 Title: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1862437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862437] [NEW] Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server
Public bug reported: Starting Ubuntu 16.10 resolution of LAN addresses fails. This name resolution failure is evident in every post 16.0 Ubuntu & derivative that I have tested. See below - which shows 16.04 resolves, 18.04 and Pop!_OS 19.04 fail, and other distros - Fedora 31, openSUSE Leap 15.1, and Debian GNU/Linux 10 (buster) - all resolve as expected. Operating System: Ubuntu 16.04.6 LTS Kernel: Linux 4.4.0-170-generic IP4.DNS[1]: 192.168.3.2 Server:127.0.1.1 Address: 127.0.1.1#53 Name: BGOWIKI01v Address: 192.168.3.60 Operating System: Ubuntu 18.04.3 LTS Kernel: Linux 4.15.0-72-generic IP4.DNS[1]: 192.168.3.2 Server:127.0.0.53 Address: 127.0.0.53#53 ** server can't find BGOWIKI01v: SERVFAIL Operating System: Pop!_OS 19.04 Kernel: Linux 5.0.0-21-generic IP4.DNS[1]: 192.168.3.2 Server:127.0.0.53 Address: 127.0.0.53#53 ** server can't find BGOWIKI01v: SERVFAIL Operating System: Fedora 31 (Workstation Edition) Kernel: Linux 5.3.7-301.fc31.x86_64 IP4.DNS[1]: 192.168.3.2 Server:192.168.3.2 Address: 192.168.3.2#53 Name: BGOWIKI01v Address: 192.168.3.60 Operating System: openSUSE Leap 15.1 Kernel: Linux 4.12.14-lp151.28.36-default IP4.DNS[1]: 192.168.3.2 Server:192.168.3.2 Address: 192.168.3.2#53 Name: BGOWIKI01v Address: 192.168.3.60 Operating System: Debian GNU/Linux 10 (buster) Kernel: Linux 4.19.0-6-amd64 IP4.DNS[1]: 192.168.3.2 Server:192.168.3.2 Address: 192.168.3.2#53 Name: BGOWIKI01v Address: 192.168.3.60 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsutils 1:9.11.3+dfsg-1ubuntu1.11 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: MATE Date: Sat Feb 8 17:36:28 2020 InstallationDate: Installed on 2019-12-22 (47 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: bind9 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862437 Title: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Yes Daniel, it is the same as shown in the screenshot in comment #3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
I've seen this same bug three times in the past two days on a new (up- to-date) ubuntu 19.10 system. The bug is NOT therefore unique to 19.04. Clicking anywhere on the dialog does in fact produce the behavior that would be appropriate for clicking whatever is below the dialog. This appears therefore to be an incorrect painting problem in gnome shell. Restarting gnome-shell ( enter r) does in fact get rid of the incorrectly painted dialog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862201] [NEW] module intel_sgx appears to be blacklisted by the kernel.
Public bug reported: In the linux-0azure kernel 5.0.0.1029 the intel_Sgx driver has become blacklisted. The directories /etc/modlprobe.d and /etc/module_load.d systemctl status systemd-modules-load.service indicates the driver is blacklisted azureuser@brcamp-oe-ubu2:~/Projects/Azure-Compute-OpenEnclave-SecureRepro$ systemctl status systemd-modules-load.service ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: active (exited) since Tue 2020-02-04 19:42:29 UTC; 1 day 20h ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 490 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS) Main PID: 490 (code=exited, status=0/SUCCESS) This is affecting azure customers. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags: linux-azure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862201 Title: module intel_sgx appears to be blacklisted by the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1862201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work
It seems a shame that my affected hardware didn't live to see this day :( If it had held on another year and a half, I would've been able to test this out. Glad Martin's was still working to check it out over _eleven years_ (!) after he first commented on this issue! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/123920 Title: Bluetooth Logitech Dinovo Keyboard/Mouse don't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860825] [NEW] can't get updates for ubuntu 19
Public bug reported: can't get updates for ubuntu 19 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Fri Jan 24 23:31:31 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860825 Title: can't get updates for ubuntu 19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504886] Re: v86d is taking 100% of 1 CPU
Now using Kubuntu 19.10 with same results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504886 Title: v86d is taking 100% of 1 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v86d/+bug/1504886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504886] Re: v86d is taking 100% of 1 CPU
Using AMCGPU driver with same results by v86d under Kubuntu 19.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504886 Title: v86d is taking 100% of 1 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v86d/+bug/1504886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841646] Re: White text on white background for HTML e-mail
** Tags added: bionic regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841646 Title: White text on white background for HTML e-mail To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1841646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841646] Re: White text on white background for HTML e-mail
Thanks for commenting. I've been meaning to mark this as "Fix Released" as the fix landed a few weeks back in 19.10 (Eoan). Looks like it will have to be backported. Unfortunately, I don't have Bug Triaging rights for Ubuntu, but hopefully some one else CC'ed in can set this to Triaged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841646 Title: White text on white background for HTML e-mail To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1841646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841646] Re: White text on white background for HTML e-mail
** Also affects: evolution via https://gitlab.gnome.org/GNOME/evolution/issues/617 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841646 Title: White text on white background for HTML e-mail To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1841646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836491] Re: Complete lock-up
I have upgraded to Kubuntu 18.04 so this is no longer an issue. You may close this ticket at your discretion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836491 Title: Complete lock-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
To expand on what Daniel said: 1. Start with one extension and remove it from Gnome Tweak Tools or the GNOME Shell Extensions web site: https://extensions.gnome.org/local/ 2. Restart GNOME Shell with ALT+F2, type in r then hit enter 3. If don't experience this bug for a few hours or days (days would be preferred) let us know in this bug report and which extension you completely removed. Perhaps we can narrow down on the problematic extension this way, if it is actually an extension. 4. If you still hit this bug a few minutes or hours later, logout from your session completely and try use the desktop for a few days. If you still have this problem try the next extension and repeat 1-3. If you have no more extensions installed and the error occurs, please consider filing a new bug report as soon as possible with ubuntu-bug gnome-shell and link the new bug report as a comment in this bug report. I hope the steps above are useful. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
