And the *release* version of Jammy has a 5.15 kernel that boots on the
machine in question, so I've managed a successful upgrade, and this
doesn't seem to be a problem for me any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update: linux-image-5.14.0-1034-oem appeared in my normal apt upgrade
today and has booted successfully, so perhaps whatever the problem was
has been fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This also happens with the kernel in xubuntu-22.04-beta-desktop-
amd64.iso, so it will block me upgrading that machine to Jammy when it's
released.
Is there anything I can do to help? I'm not familiar with debugging
kernel drivers, but I'm a competent general developer, and I'm prepared
to put in
I don't really know what information I should be reporting about my
hardware. My first guess is that the output of 'lspci -v' relating to
the video device might be useful, so here it is:
00:02.0 VGA compatible controller: Intel Corporation Device 4c8a (rev 04) (prog-
if 00 [VGA controller])
** Attachment added: "dmesg.nomodeset.5.14.0-1031-oem.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+attachment/5574751/+files/dmesg.nomodeset.5.14.0-1031-oem.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "dmesg.success.5.11.0-46-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+attachment/5574752/+files/dmesg.success.5.11.0-46-generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has
been working fine for me (and supported the network device on my
reasonably recent PC, which 20.04's default kernel didn't). But the 5.13
and 5.14 kernels all hang on boot.
If I edit the GRUB boot commands
Public bug reported:
Linphone crashes at startup for me, if too many audio devices are
connected, with a message on stderr saying
free(): double free detected in tcache 2
SIGABRT / SIGIOT: Aborted
I debugged the problem and found that the crash was occurring in the
libmediastreamer_voip.so.10
I've also had this problem with Audacity since updating from 18.04 to
20.04, and indeed, removing GTK_IM_MODULE=xim from the environment
worked around it.
However, that's not a great workaround for me, because I put that in the
environment on purpose. Without it, GTK2 applications don't honour
Now I think about it harder, I suppose I should mention a few more
details.
On the test VM I spun up for the reproducer, I was doing all of this by
logging in on a text virtual console. On the real machine where I had
this problem originally, I'm doing remote working by SSHing in, running
Public bug reported:
I work remotely by running an XFCE session inside an X display created
by vnc4server. On Ubuntu xenial, this causes xfce4-notifyd to fail to
start up.
A transcript of my VNC startup script and the results:
simon@xenial:~$ cat ~/.vnc/xstartup
#!/bin/sh
exec setsid
11 matches
Mail list logo
