Probably xwayland as my setup does not involve running xorg. Or gnome: why is
org.gnome.SettingsDaemon.XSettings.service needed on Wayland? Gnome does not
use xwayland to run itself, it runs on wayland natively.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
When I think about it now, I started to suspect that the Wayland
compositor in Gnome went wacko when the GPU reset occured.
Unfortunately, I can't replicate this as I have no idea how to easily
trigger a GPU reset. Generally submitting a GPU load that overloads it
should do the trick but
Ok, now I realized that my system runs on Wayland. So no xorg problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066187
Title:
org.gnome.SettingsDaemon.XSettings.service fails to restart
Public bug reported:
GNOME did not recover successfully from a GPU reset event. The system is
still running but no direct interaction with it is possible. Keyboard
appears to be running but the screen shows what was on it when the GPU
crashed.
Attached is a SYSLOG fragment showing the problem.
It looks the syslog fragment I was talking about in the bug report got
lost in the bug submission process. Here it is.
** Attachment added: "SYSLOG fragment showing symptoms of the problem"
https://bugs.launchpad.net/ubuntu/+bug/2066187/+attachment/5780125/+files/syslogfragment
--
You
** Also affects: gdm3 (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/1832436
Title:
login page first appears sideways for Lenovo miix 510 ubuntu
Public bug reported:
This might be also bug in pulse-audio. The problem
manifests in these ways:
Scenario 1:
1. Assuming output is to a built-in speaker, set the
volume to non-100%.
2. Connect an audio output device (e.g. headphones).
3. Set the volume to non-100% but visibly different from
The chromium-browser metadata needs fixing (as explained in my last
comment) so that libnss3 gets upgraded automatically on "apt-get install
chromium-browser".
** Changed in: chromium-browser (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member
> chromium-browser requires a newer version of libnss3 than what was
initially installed.
It is the job of the package manager to either upgrade an outdated
version of a dependency package when the user tries to install something
or to ask the user to update the system first and then try again,
Public bug reported:
Steps to reproduce (and also what I expected and what happened):
1. Disconnect computer from Internet
2. Install Ubuntu (complete with reboot at the end).
3. After running the (freshly installed) system, connect it to Internet
and open a terminal and follow with the
The additional attached information was sampled at the time after the
chromium-browser successfully completed its install (and after that was
confirmed by successfully launching it as shown in the terminal session)
so any traces of its misbehavior might be long gone before the
attachments were
Public bug reported:
The attached program exposes a bug in posix_memalign that causes it to
either silently corrupt heap or cause the memory allocation checker to
report spurious failures. I believe that the former is the case here
because on more complex software (minetest or Irrlight tutorial
12 matches
Mail list logo
