[Bug 2057805] Re: On Noble, system is locking up when attempting to log back in after being away for a few minutes
Just wanted to say, this is still happening regularly to me. I can work around it if I remember to put the system in suspend rather than simply locking the screen, but if I lock the screen and walk away for too long, the system is locked up aside from the alt-sysrq keys. I have a system where I can readily reproduce the issue and am happy to work with devs re: testing or possible fixes; would love to get this fixed before noble goes out the door. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057805 Title: On Noble, system is locking up when attempting to log back in after being away for a few minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057805] [NEW] On Noble, system is locking up when attempting to log back in after being away for a few minutes
Public bug reported: Context: On my laptop, connected to battery power, if I lock the screen and come back sometime later (likely after the 10 minute "screen blank" threshold I have set in Gnome), I find that it does not come back up properly. * I have 3 monitors (2 external and one built-in), and when I move my mouse to wake up my machine, only the wallpaper on the built-in display seems to come back. * I get no login prompt. * I have no visible mouse cursor, and pressing Num Lock on my keyboard doesn't toggle any lights on the keyboard. * Ctrl-Alt-F1, -F2, etc., do not work. * The only way I know to get out of this is to either hard-reboot the machine or use the Alt-SysRq keys (e.g. the "reisub" combination). * /var/log/syslog and kern.log do show a general protection fault. Actually, 3 of them. (I had at least 3 lockups yesterday.) I've attached one as general_protection_fault.txt here; hopefully "ubuntu-bug linux" could capture the others if they are helpful. Additional context in case it is helpful: * I recently upgraded from Mantic to Noble for the purpose of dogfooding prior to formal release. I had some problems on Mantic with stability which had similar crashes, but they were more intermittent and did not generate the protection faults in syslog. Since upgrading to Noble, the lockups have changed from intermittent to predictable, i.e. if I lock my screen and walk away for at least 10 minutes, I fully expect to have to reboot my machine. I am running the 2013 model of the ASUS ROG M16 Zephyrus. It does use Nvidia Optimus, and while I suspect the problems I was encountering on Mantic were perhaps due to Nvidia driver bugs, the issues in Noble do appear to be different since the crashes are more consistent and appear to also generate the general protection fault errors in syslog. (I explain this since without this nuance, it may be easy to just suspect the nvidia driver is causing the problem.) Hopefully this helps; let me know if there's anything else I can provide to assist with this bug. Best Regards, Paul Goins ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 08:30:23 2024 InstallationDate: Installed on 2023-09-11 (184 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus M16 GU604VI_GU604VI ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=c8e79db4-8ec5-4855-89b4-aea8fb2c5b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-07 (6 days ago) dmi.bios.date: 09/07/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GU604VI.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU604VI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.68 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGU604VI.312:bd09/07/2023:br5.27:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGZephyrusM16GU604VI_GU604VI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU604VI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus M16 dmi.product.name: ROG Zephyrus M16 GU604VI_GU604VI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "general_protection_fault.txt" https://bugs.launchpad.net/bugs/2057805/+attachment/5755616/+files/general_protection_fault.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057805 Title: On Noble, system is locking up when attempting to log back in after being away for a few minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882794] Re: do-release-upgrade should allow other tools to block or warn before upgrades
This would be immensely helpful. Please note that I'm commenting as a member of Canonical's BootStack team, where we regularly use Juju, i.e. case 1 listed above. When I'm managing a cloud with Juju, and need to do a series upgrade, Juju requires that certain hooks are run prior to performing the do- release-upgrade. If these hooks are not fired, the effects can be fairly serious. A key example is the use of Python virtualenvs in many charms, especially "reactive" Juju charms. These virtualenvs link into the system Python, and special care must be taken at upgrade time for the virtualenvs to be recreated against the new Ubuntu release's Python, else the virtualenv will become unusable after the upgrade is completed. That's part of the reason for Juju's "upgrade-series" commands. However, it is very easy for an engineer (read: me) to accidentally miss a step, perform the do-release-upgrade, and realize after the fact that my action resulted in breaking management of the Juju-managed applications deployed on the target machine. And this is actually worse than just that, as often you can't even cleanly remove the affected applications because of the broken virtualenvs. The solution is often to completely redeploy the affected machine by force, which may also has impact on related machines which couldn't communicate with the forcefully redeployed unit during teardown. The above may not be clear to those who aren't deeply familiar with Juju, but put more simply: not being able to enforce running of Juju's actions prior to upgrade is a risk to Juju-deployed clouds. If we could have a way for Juju to install a hook, or even simply a "do not run" breadcrumb, so that do-release-upgrade could be blocked until Juju has had a chance to run its pre-release hooks, that would allow Juju to have much more robust series upgrades of Juju managed machines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882794 Title: do-release-upgrade should allow other tools to block or warn before upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1882794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Re: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
Just had a recurrence. This happened when doing a series upgrade from bionic/ussuri to focal/ussuri. All compute nodes have /var/lib/nova/.ssh/id_rsa with 0644 permissions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943898] [NEW] docker.io modifies routing rules in a way which breaks LXD bridge
Public bug reported: I was trying to bootstrap a Juju controller on LXD. Unfortunately, this never finished, and upon further investigation, I found that none of my LXD containers could reach the Internet via the configured bridge, lxdbr0. This was working previously, but recently I installed docker.io. I stopped and/or removed other components which were installing routing rules, e.g. microk8s and multipass, but nothing resolved the problem until I removed docker.io and restarted my computer. Long story short, I traced down the reason why this wasn't working to a routing rule. I dumped my iptables rules while docker.io was uninstalled and things were working, and then dumped again after I installed docker.io and rebooted. (The reboot was necessary; things still worked after installing docker.io, but stopped working after reboot.) Here is the key diff that I saw: [...] + sudo iptables -tfilter -S -P INPUT ACCEPT --P FORWARD ACCEPT +-P FORWARD DROP [...] I could manually run "sudo iptables -tfilter -P FORWARD ACCEPT" to make things work again. (Obviously that may not be the best workaround for security reasons, but LXD doesn't seem to install rules sufficient for routing to still work after docker.io makes this change.) I'll leave it up to you whether this is a docker.io bug or an lxd bug, but it was installation of docker.io which triggered the situation for me. Relevant information: $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy docker.io | head -n2 docker.io: Installed: 20.10.7-0ubuntu1~20.04.1 Expected behavior: being able to use LXDs like normal without loss of Internet connectivity after installing docker.io package. What happened instead: lost Internet connectivity due to change in filter table's -P FORWARD rule. Best Regards, Paul Goins ** Affects: docker.io (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/1943898 Title: docker.io modifies routing rules in a way which breaks LXD bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1943898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914447] Re: geneve overlay network on vlan interface broken with offload enabled
I found this bug listed in a doc for a customer environment running Bionic, as something that was affecting them as well and for which we were waiting for a fix. I noticed today that this bug is only marked for focal and groovy. Is there a reason for this to be only focal and newer, or is it simply that it hadn't been reported for bionic yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914447 Title: geneve overlay network on vlan interface broken with offload enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894843] Re: [dvr_snat] Router update deletes rfp interface from qrouter even when VM port is present on this host
We are encountering this on bionic/stein; is a backport in the works? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894843 Title: [dvr_snat] Router update deletes rfp interface from qrouter even when VM port is present on this host To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1894843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918314] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1918314/+attachment/5475469/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918314 Title: Cannot boot from grub after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918314] Re: Cannot boot from grub after upgrade
apport information ** Description changed: Since upgrading from Focal, it seems that I'm hitting boot problems every time Grub is ugpraded. For context, I recently upgrade from Focal to Groovy, then on the same day, to Hirsute (prerelease). On the upgrade to Groovy, my system stopped booting to grub, and I needed to load a Groovy install USB and run "grub-install" to make my system bootable. (More specifically: grub-install --uefi-secure-boot --boot-directory= --efi-directory=/efi) On the upgrade to Hirsute, the same thing occurred, and I had to repeat the same to be able to boot. And after package upgrades yesterday, when I powered on my machine today, the same thing occurred again, so I gathered some details this time around. The following grub packages changed during last night's upgrade: grub-pc-bin:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44) grub-efi-amd64-signed:amd64 (1.163+2.04-1ubuntu40 -> 1.166+2.04-1ubuntu44) grub-efi-amd64-bin:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44) grub-common:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44) grub-pc:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44) As context, my system uses EFI (secure boot on if I recall right), and my disk is partitioned as follows: Device StartEnd Sectors Size Type /dev/sda1 20481050623 1048576 512M EFI System <- /boot/efi /dev/sda210506242549759 1499136 732M Linux filesystem <- /boot /dev/sda32549760 500632903 498083144 237.5G Linux filesystem <- / (encrypted LVM) /dev/sda4 500633600 500666367 3276816M Microsoft reserved /dev/sda5 500666368 999149401 498483034 237.7G Microsoft basic data /dev/sda6 999149568 1000212479 1062912 519M Windows recovery environment Also, note that simply doing "sudo update-grub" does *not* trigger this problem. It seems to be something which happens at upgrade time. - Please let me know if there's any other info I can gather for this; I - fully expect this problem to recur the next time grub gets upgraded as - well. + Please let me know if there's any other info I can gather for this; I fully expect this problem to recur the next time grub gets upgraded as well. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu59 + Architecture: amd64 + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2019-01-04 (796 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: grub2 (not installed) + ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 + SourcePackage: grub2 + Tags: hirsute + Uname: Linux 5.10.0-14-generic x86_64 + UpgradeStatus: Upgraded to hirsute on 2021-03-02 (8 days ago) + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1918314/+attachment/5475468/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918314 Title: Cannot boot from grub after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918314] Re: Cannot boot from grub after upgrade
Additionally, tried grub-install directly from within hirsute: root@dell2018:~# grub-install Installing for x86_64-efi platform. Installation finished. No error reported. When I reboot... same problem. Had to again recover via the USB installer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918314 Title: Cannot boot from grub after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918314] Re: Cannot boot from grub after upgrade
Hit Enter too soon on my previous comment. The "dpkg-reconfigure grub- efi-amd64-signed" reproduced the issue, and again, had to grub-install via a hirsute USB install disk. (Same command as previously reported, although I dropped --uefi-secure-boot this time around out of curiosity, and it still worked.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918314 Title: Cannot boot from grub after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918314] Re: Cannot boot from grub after upgrade
1. I ran dpkg-reconfigure as requested; here's what I saw: root@dell2018:~# dpkg-reconfigure grub-efi-amd64-signed Installing grub to /boot/efi. Installing for x86_64-efi platform. Installation finished. No error reported. 2. I ran "apport-collect 1918314", and it appears to have set the apport-collected tag here, but it also gave me a traceback and a 400: Bad Request error. Should I retry that, or are there other specific flags I should be trying? ** Tags added: apport-collected hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918314 Title: Cannot boot from grub after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918273] Re: I can't move the windows on Ubuntu 21.04
Attempting to attach a screen capture video. ** Attachment added: "simplescreenrecorder-2021-03-09_08.18.31.mkv" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+attachment/5475163/+files/simplescreenrecorder-2021-03-09_08.18.31.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918273 Title: I can't move the windows on Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918273] Re: I can't move the windows on Ubuntu 21.04
I've encountered the same problem today. I did a little more testing, and I've observed other issues as well, some which may be related, arguably some which may be separate bugs, but I'll list them nonetheless: * Cannot move gnome-terminal windows by dragging the title bar. * Right clicking the gnome-terminal title bar opens the context menu, but it disappears as soon as the right mouse button is released. (As a partial workaround for the first bullet: If I hold the right mouse button, go down to "Move", and then release it, it activates the Move option and I can move the window.) * Other windows (firefox snap, emacs) won't switch focus back to gnome-terminal easily unless you resize the window a little bit, after which they'll allow you to do so. Strangely, the same problem doesn't extend to switching between snapped firefox and emacs. * alt-tab doesn't show any visual overlay, and only switches between the last 2 windows. * Toggling a VPN connection via the top right hand corner menu will cause a crash and reload of the UI. (I just toggled my connection to the Canonical VPN twice, and each time I did so, this happened.) I don't know if there's a shared underlying library that this is all related to or not; maybe these issues need to be broken apart. Nonetheless, reporting this so at least we have the info somewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918273 Title: I can't move the windows on Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918314] [NEW] Cannot boot from grub after upgrade
Public bug reported: Since upgrading from Focal, it seems that I'm hitting boot problems every time Grub is ugpraded. For context, I recently upgrade from Focal to Groovy, then on the same day, to Hirsute (prerelease). On the upgrade to Groovy, my system stopped booting to grub, and I needed to load a Groovy install USB and run "grub-install" to make my system bootable. (More specifically: grub-install --uefi-secure-boot --boot-directory= --efi-directory=/efi) On the upgrade to Hirsute, the same thing occurred, and I had to repeat the same to be able to boot. And after package upgrades yesterday, when I powered on my machine today, the same thing occurred again, so I gathered some details this time around. The following grub packages changed during last night's upgrade: grub-pc-bin:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44) grub-efi-amd64-signed:amd64 (1.163+2.04-1ubuntu40 -> 1.166+2.04-1ubuntu44) grub-efi-amd64-bin:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44) grub-common:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44) grub-pc:amd64 (2.04-1ubuntu40 -> 2.04-1ubuntu44) As context, my system uses EFI (secure boot on if I recall right), and my disk is partitioned as follows: Device StartEnd Sectors Size Type /dev/sda1 20481050623 1048576 512M EFI System <- /boot/efi /dev/sda210506242549759 1499136 732M Linux filesystem <- /boot /dev/sda32549760 500632903 498083144 237.5G Linux filesystem <- / (encrypted LVM) /dev/sda4 500633600 500666367 3276816M Microsoft reserved /dev/sda5 500666368 999149401 498483034 237.7G Microsoft basic data /dev/sda6 999149568 1000212479 1062912 519M Windows recovery environment Also, note that simply doing "sudo update-grub" does *not* trigger this problem. It seems to be something which happens at upgrade time. Please let me know if there's any other info I can gather for this; I fully expect this problem to recur the next time grub gets upgraded as well. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918314 Title: Cannot boot from grub after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917424] Re: LVM2 hook not executable; causes update-initramfs to miss adding lvm2 binaries
Also, for completeness: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Hirsute 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 2.03.11-2ubuntu2 3) What you expected to happen To be able to build a working initramfs to boot Ubuntu after upgrade. 4) What happened instead initramfs was missing the lvm2 binary and did not pick up my LVs after I decrypted the partition which hosted them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917424 Title: LVM2 hook not executable; causes update-initramfs to miss adding lvm2 binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917424] [NEW] LVM2 hook not executable; causes update-initramfs to miss adding lvm2 binaries
Public bug reported: I did an upgrade from Groovy to Hirsute today, but the upgrade did not go well. I run an encrypted LVM for my root Ubuntu partition. My grub did not get updated properly at upgrade time, but via a USB startup disk for Hirsute I was able to repair this myself. However, I spent hours trying to get grub to detect my LVs. Ultimately, I found the problem: /usr/share/initramfs-tools/hooks/lvm2 in the lvm2_2.03.11-2ubuntu2_amd64.deb package lacks an executable flag. Running update-initramfs verbosely highlighted that the hook was not getting fired for this reason. Upon adding the executable flag to the file, I was able to use a chroot to re-build the initramfs and get my system to boot. ** Affects: lvm2 (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/1917424 Title: LVM2 hook not executable; causes update-initramfs to miss adding lvm2 binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789177] Re: RabbitMQ fails to synchronize exchanges under high load
I think UCA/Queens should be changed from "fix committed" to "fix released"; we just applied this to a customer cloud today, however at first we mistakenly thought it hadn't been released yet. (By the way, it resolved the customer's issue, so there's another "works on Bionic/Queens" datapoint.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789177 Title: RabbitMQ fails to synchronize exchanges under high load To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895893] [NEW] Python 3 variable scoping issue is hiding error tracebacks
Public bug reported: A script my team uses python3-amqplib for RabbitMQ connectivity checking, but in the case of not being able to connect, the error we get when running from Python 3 hides the real problem behind a Python 3 variable scoping issue. This is reproducible via: python3 -c "from amqplib import client_0_8 as amqp; amqp.Connection()" The above will generate this output (assuming no RabbitMQ is running on your system): Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/amqplib/client_0_8/connection.py", line 129, in __init__ self.transport = create_transport(host, connect_timeout, ssl) File "/usr/lib/python3/dist-packages/amqplib/client_0_8/transport.py", line 281, in create_transport return TCPTransport(host, connect_timeout) File "/usr/lib/python3/dist-packages/amqplib/client_0_8/transport.py", line 85, in __init__ raise socket.error(msg) UnboundLocalError: local variable 'msg' referenced before assignment I would instead expect the following, which I see on Bionic when running the same command from above, but via Python 2 instead: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py", line 129, in __init__ self.transport = create_transport(host, connect_timeout, ssl) File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/transport.py", line 281, in create_transport return TCPTransport(host, connect_timeout) File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/transport.py", line 85, in __init__ raise socket.error, msg socket.error: [Errno 111] Connection refused In Python 2, we get "Connection refused" - in Python 3, we get a Python error, which hides the "Connection refused" message. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-amqplib (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 16 14:08:00 2020 InstallationDate: Installed on 2019-01-04 (621 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: python-amqplib UpgradeStatus: Upgraded to focal on 2020-01-31 (229 days ago) ** Affects: python-amqplib (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/1895893 Title: Python 3 variable scoping issue is hiding error tracebacks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-amqplib/+bug/1895893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
The issue did not occur after logging out and back in. I'll cycle through a few times to see if it recurs... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
Hello, This morning, interestingly enough, despite having renamed my .xinitrc to .xinitrc.bak, I ended up with the same glitch. It may be the issue is slightly intermittent and I had thought I had repaired it for myself, but in actuality I had not. I'll try doing what you suggested; just a moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
I just did 4 more logins, so that's 5 logins since moving ~/.mozc to ~/.mozc.bak. First 4 logins: all good. 5th login: the issue recurred. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
Yes, the issue recurs after logging back in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
Certainly; I'm happy to provide more input. "Are you running Ubuntu on Xorg or Ubuntu on Wayland?" Ubuntu on Xorg. Just straight default Gnome 3 environment. I have installed other environments (e.g. i3), but I don't actively use them. "Can you please check the environment variables [...]" paul-goins@dell2018:~$ env | grep -E 'XMOD|_IM' GTK_IM_MODULE=ibus QT4_IM_MODULE=ibus XMODIFIERS=@im=ibus CLUTTER_IM_MODULE=ibus QT_IM_MODULE=ibus "Also, it would be valuable if you could create ~/.xinputrc again" Ran "im-config -n ibus" as directed. I'll update after I log back in later tonight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
Pastebin w/ more context, for what it's worth: https://pastebin.ubuntu.com/p/9cJpFDwMV4/ i.e. I had run im-config at some time in the past, and it had set things up... but apparently that file is no longer appropriate for my setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
Hello, I have repaired this on my side. It seems I had an ~/.xinputrc file present on my system, and this seems to interfere with how things currently run. The ~/.xinputrc had this line: run_im ibus I renamed it to ~/.xinputrc_bak and logged out and back into my account; now everything is working as expected again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
No, the issue is *not* present with a newly created user. ...I wonder what could be tripping this up on my account then... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
I did the apt commands you suggested, verbatim, then did a reboot. Unfortunately that did not resolve it. It is ibus-mozc that is in use, to be clear. Also, here's a pastebin of relevant "dpkg -l | grep " queries: https://pastebin.ubuntu.com/p/hYFDYbyxhp/ And the environment output: paul-goins@dell2018:~$ env | grep -E 'XMOD|_IM' GTK_IM_MODULE=ibus QT4_IM_MODULE=ibus XMODIFIERS=@im=ibus CLUTTER_IM_MODULE=ibus QT_IM_MODULE=ibus Hope this helps, and of course, let me know if there's any other information I can provide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
The issue appears to be consistently reproducible on my system. I booted twice this morning, and it came up both times on top of where the Gnome menu is. While I think I've probably adequately explained it, I did take a video during boot-up as well, just to avoid any ambiguity on what I'm seeing. I'll attach it shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
** Attachment added: "Video of startup, showing the bug" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+attachment/5343822/+files/20200331_080627.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] Re: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
Hello, Actually, that appeared before Emacs was launched. I wasn't thinking about Emacs-specific IME interactions, but in this case that's not the case. I'll try a few restarts of my system to see whether this is reproducible on my side; again, I saw it and just wanted to be especially proactive about filing since I felt I'd otherwise get sucked into other work and possibly forget about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869752] [NEW] mozc selector GUI showing on top of gnome 3 GUI in latest focal packages
Public bug reported: Hello, Today, I updated to the latest packages for focal. I use Gnome 3 with mozc for Japanese input. The problmem I saw, and I'm not sure if this is intermittent or not yet, is that the mozc gui showed up on top of the top right corner of my primary monitor. (Normally Gnome 3 hides it.) I was unable to access the menus beneath it, and I couldn't seem to drag the overlay except via a very small corner of pixels which was not overlapping Gnome's top bar. Since there is that corner by which the overlay can be dragged, this doesn't seem critical (at least not on my personal display), but this does seem like an unintentional regression. ...And again, I'm not yet certain whether this is intermittent or on every boot. I'm just making sure to file this while it's fresh in my head. Screenshot attached. ** Affects: mozc (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot showing overlay blocking wifi and Gnome menus" https://bugs.launchpad.net/bugs/1869752/+attachment/5343409/+files/Screenshot%20from%202020-03-30%2008-16-06_onemonitor.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869752 Title: mozc selector GUI showing on top of gnome 3 GUI in latest focal packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1869752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491719] Re: scim can not be triggered in the emacs 23 when lang is set to zh_CN.UTF-8
Something similar, maybe not the same, also happens with Japanese. My locale is en_US.UTF-8, and in Emacs 22 I can use SCIM for Japanese input no problem. On Emacs 23, no luck. If I do the locale fix like above, in my case LC_CTYPE=ja_JP.UTF-8 emacs, it works on Emacs 23 as well. -- scim can not be triggered in the emacs 23 when lang is set to zh_CN.UTF-8 https://bugs.launchpad.net/bugs/491719 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
