[Bug 1947028] Re: apt update failing with NO_PUBKEY in Ubuntu 20.04
** Attachment added: "ubuntu-advantage.log.1" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1947028/+attachment/5532561/+files/ubuntu-advantage.log.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947028 Title: apt update failing with NO_PUBKEY in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1947028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947028] [NEW] apt update failing with NO_PUBKEY in Ubuntu 20.04
Public bug reported: Installed ubuntu-advantage-tools in Ubuntu 20.04 and am unable to run apt-update. sudo apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 27.2.2~20.04.1 Candidate: 27.2.2~20.04.1 Version table: *** 27.2.2~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 20.3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ua status SERVICE ENTITLED STATUS DESCRIPTION cis yes disabled Center for Internet Security Audit Tools esm-infra yes disabled UA Infra: Extended Security Maintenance (ESM) fips yes disabled NIST-certified core packages fips-updates yes disabled NIST-certified core packages with priority security updates livepatch yes disabled Canonical Livepatch service sudo apt update Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease Get:2 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:3 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB] Get:4 http://us.archive.ubuntu.com/ubuntu focal-security InRelease [114 kB] Get:5 https://esm.ubuntu.com/fips/ubuntu focal InRelease [3,878 B] Get:6 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [1,260 kB] Get:7 http://us.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [865 kB] Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [24.7 kB] Err:5 https://esm.ubuntu.com/fips/ubuntu focal InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C1997C40EDE22758 Reading package lists... Done W: GPG error: https://esm.ubuntu.com/fips/ubuntu focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C1997C40EDE22758 E: The repository 'https://esm.ubuntu.com/fips/ubuntu focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-advantage.log" https://bugs.launchpad.net/bugs/1947028/+attachment/5532560/+files/ubuntu-advantage.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947028 Title: apt update failing with NO_PUBKEY in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1947028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937089] Re: System76 - systemd and gnome errors, crash with black screen
Here is a sosreport of the affected system. ** Attachment added: "sosreport of affected system" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937089/+attachment/5512592/+files/sosreport-blackscreen.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937089 Title: System76 - systemd and gnome errors, crash with black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937089] [NEW] System76 - systemd and gnome errors, crash with black screen
Public bug reported: I'm uncertain if this is specific to System76, or if it is resulting from an error in systemd or gdm3. Symptoms: Unprompted, screen will go black, and then bring you back to the login screen. Upon entering the password to log back in you're brought back to a black screen. Hitting ctrl+alt+f5 I'm able to get back to a terminal, login, and restart gdm to be brought back to the desktop (sudo systemctl restart gdm) Specs: System76 Darter Pro inxi CPU: Quad Core Intel Core i7-10510U (-MT MCP-) speed/min/max: 1195/400/4900 MHz Kernel: 5.11.0-7620-generic x86_64 Up: 30m Mem: 5091.7/31984.5 MiB (15.9%) Storage: 465.76 GiB (76.2% used) Procs: 371 Shell: bash 5.0.17 inxi: 3.0.38 lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Logs From /var/log/syslog at the time of the disruption: Jul 21 08:18:36 user-Darter-Pro systemd-resolved[1289]: Freeing transaction 62282. Jul 21 08:18:38 user-Darter-Pro systemd[1]: We couldn't coldplug machine-qemu\x2d1\x2dubuntu20.04.scope, proceeding anyway: Connection timed out Jul 21 08:18:38 user-Darter-Pro systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro NetworkManager[1364]: [1626873518.6564] caught SIGTERM, shutting down normally. Jul 21 08:18:38 user-Darter-Pro systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: switcheroo-control.service: Succeeded. Jul 21 08:18:38 user-Darter-Pro systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro thermald[1409]: Terminating ... Jul 21 08:18:38 user-Darter-Pro system76-power[1406]: [INFO] caught signal: SIGTERM Jul 21 08:18:38 user-Darter-Pro systemd[1]: system76-power.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Got SIGTERM, quitting. Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-machined.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe01:19ab. Jul 21 08:18:38 user-Darter-Pro kernel: [ 2399.879916] wlp0s20f3: deauthenticating from 30:23:03:db:ac:19 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 21 08:18:38 user-Darter-Pro ModemManager[1518]: Caught signal, shutting down... Jul 21 08:18:38 user-Darter-Pro systemd[1]: avahi-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro pulseaudio[2373]: X connection to :0 broken (explicit kill or server shutdown). Jul 21 08:18:38 user-Darter-Pro systemd[1]: ModemManager.service: Unexpected error response from GetNameOwner(): Connection terminated Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663429:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663447:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro chromium_chromium.desktop[4790]: [4790:4790:0721/081838.663498:ERROR:pulse_util.cc(343)] pa_operation is nullptr. Jul 21 08:18:38 user-Darter-Pro bluetoothd[1357]: Terminating Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): flip queue failed: Permission denied Jul 21 08:18:38 user-Darter-Pro /usr/lib/gdm3/gdm-x-session[2471]: (WW) modeset(0): Page flip failed: Permission denied Jul 21 08:18:38 user-Darter-Pro systemd[1]: systemd-machined.service: Succeeded. Jul 21 08:18:38 user-Darter-Pro wpa_supplicant[1411]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=30:23:03:db:ac:19 reason=3 locally_generated=1 Jul 21 08:18:38 user-Darter-Pro gnome-shell[2614]: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Jul 21 08:18:38 user-Darter-Pro avahi-daemon[1355]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jul 21 08:18:38 user-Darter-Pro systemd[1]: polkit.service: Unexpected error response from
[Bug 1922277] [NEW] Feature Request: UbuntuCore20 - snap set command to configure journald
Public bug reported: Request: Similar to documented [1] snap set commands, could there be a configuration parameter available to limit log storage to 512MB? [1] - https://snapcraft.io/docs/system-options#heading--journal- persistent Workaround used (but would prefer a snap set command for this functionality): Clean the logs to the requested size utilizing the journalctl vacuum capabilities, for example: journalctl --vacuum-size=512M If you have access to edit /etc/systemd/journald.conf file you could set the parameter SystemMaxUse= to 512M, however in Ubuntu Core this may be read-only and unalterable. If that is the case use a systemd timer or cron job to manage the file size with the journalctl command provided above. ** Affects: ubuntu Importance: Undecided Status: New ** Project changed: brz => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922277 Title: Feature Request: UbuntuCore20 - snap set command to configure journald To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1922277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Attached is the output to lspci -k from another user experiencing this issue. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874567/+attachment/5382948/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Attached is the output from lshw -C display from a user experiencing this bug ** Attachment added: "lshw.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874567/+attachment/5382949/+files/lshw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
