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
nt 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
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
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.
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:
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
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
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
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
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
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
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
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
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
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
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
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
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.)
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
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
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
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
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
nment 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
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
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
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
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:
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
** 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.
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
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
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
33 matches
Mail list logo
