I have the same issue after a recent kernel update. Not sure if the
cause is the same, but after about 5 hours looking to the issue, the
mostly likely cause seems well explained on this bug comment:
https://bugzilla.kernel.org/show_bug.cgi?id=208061#c5
In my case.
Distro v: 20.04.6 LTS
Kernel v:
Another correction. For the one workaround, switching to discrete
graphics in the BIOS only seemed to get past the initial gnome login.
But resuming from DPMS off/suspend, the same error loop happens even
when hybrid graphics is disabled in the BIOS.
Even worse, seems hardware acceleration ends up
Apologies, continuing the comment above (mistakenly posted when adding
the log attachment). Let me retry.
Failure loop observed:
- Failed to blit shared framebuffer: EGL failed to allocate resources for the
requested operation.
- Failed to set CRTC mode 3840x2160: No such file or directory
To s
Here's the script I run to workaround the intital failure of gnome to
use the external display after unlocking or resuming from DPMS
suspend/off.
** Attachment added: "fix-hdmi-uhd.sh"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh
--
Y
Hi, thanks to everyone, especially Daniel for unpacking this issue.
I have had a very similar issue, where gnome shell fails to run my
external 4K/UHD display at 60HZ and I see the following failure loop
triggered in `journalctl -b -p warning _COMM=gnome-shell`:
May 02 20:39:38 JNBA434499PLL gno
It's a shot in the dark, but in my case, pulse sound server (atop of
alsa) seems to have gotten into a mess with an upgrade between 16.04 and
18.04. Post login, removing old / session start user config fixed my
dodgy channel mappings (but not quite the same as crackling, etc):
pulseaudio --kill \
Wish there was a "needs more info" tag or a way to tag bug reports like
this. There's no context as to exactly what the problem is despite the
alsa-info script output being supplied.
It's unfair to maintainers to expect them to fish out the problem.
"Sound bug ubuntu 18.04" is way too generic.
--
See
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774904/comments/4.
gnome-control-center should rather add libcanberra-pulse to depends
rather than just recommends.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi, in my case, I think it was simply a missing package dependency.
Installing the libcanberra-pulse package fixed it for me.
gnome-control should probably add libcanberra-pulse to a proper
dependency rather than just recommends since it's likely common that
people would want to test speakers and
Update on the previous comment, I realised the issue was the the
partition where /var was mounted to hat nosuid set. Seems /var/lib/lxc
must allow for the suid bit to be set. The problem is that people often
have /home mounted with nosuid as a normal security precaution, so this
effects running unp
It also affected me on Ubuntu 16.04 LTS with /var/lib/lxc mount via
bind.
My original setup only had 8GB for /var, so a bind to directory in /home
was the custom hack I did to give lxc more space.
$ grep lxc /etc/fstab
/home/var/lib/lxc /var/lib/lxc nonebind
11 matches
Mail list logo
