** Summary changed:
- gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in
cso_destroy_context() [r300_dri.so]
+ gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in
cso_destroy_context() [r300_dri.so]
--
You received this bug notification because you are
Can anyone please give a summary of the solution? What works what does not? I
am using 5.11rc7 on ubuntu 20.04. The touchpad works (not great though) but I
cannot use nvidia gpu, hence stuck with the iGPU. The brightness control does
not work perfectly. Is it possible to able to use touchpad and
Can anyone please give a summary of the solution? What works what does not? I
am using 5.11 on ubuntu 20.04. The touchpad works (not great though) but I
cannot use nvidia gpu, hence stuck with the iGPU. The brightness control does
not work perfectly. Is it possible to able to use touchpad and th
Hi Shatadru Banerjee (satadru-bag)
I think you should stick to patches and an official kernel of your
distro for now.
I use Pop OS 20.10 with kernel 5.8.*. I used to apply the patch in
comment #171 and rebuild the kernel to fix my touchpad.
Now two of the 3 new patches which Coiby Xu mentions in
@Alex: there should still be a progress dialog, regardless of the power
profile.
Do you have the new nvidia-settings package?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1915003
Tit
@Łukasz I verified LP: #1904583
Also, the reason why I moved self._disable_nvidia() down is that we want
the other stuff that ends up in the modprobe conf file (from
self._enable_runtimepm() and self._enable_kms()) to take place before we
update the initramfs, which we do in self._disable_nvidia()
Public bug reported:
Update the 460 driver, make switching between driver series more robust
(LP: #1915935), and add support for Linux 5.11
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the
** Description changed:
Update the 460 driver, make switching between driver series more robust
(LP: #1915935), and add support for Linux 5.11
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvem
** Description changed:
Update the 460 driver, make switching between driver series more robust
(LP: #1915935), and add support for Linux 5.11
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvem
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1916908
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Description changed:
Update the 460 driver, make switching between driver series more robust
(LP: #1915935), and add support for Linux 5.11
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvem
** Description changed:
Update the 460 driver, make switching between driver series more robust
(LP: #1915935), and add support for Linux 5.11
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvem
** Description changed:
Update the 460 driver, make switching between driver series more robust
(LP: #1915935), and add support for Linux 5.11
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvem
Public bug reported:
UBUNTU 20.04.2 updated until 02/25/2021
5.8.0-44-generic kernel
xorg version: 1:7.7+19ubuntu14
I expected to have a minimally acceptable performance, just as it was
before the update.
The problem only happens in sessions with XORG, either through the GNOME
or UBUNTU sessio
Public bug reported:
It looks an awful lot like this issue :
https://gitlab.freedesktop.org/drm/amd/-/issues/1427.
I'm hitting these:
[11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR*
dce112_get_pix_clk_dividers: Invalid parameters!!
[11596.269781] [drm:dm_restore_drm_connector_s
** Attachment removed: "a"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1916948/+attachment/5467211/+files/a
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1916948
Title:
AMD. Extreme
Public bug reported:
When hirsute-proposed is enabled (works fine in hirsute), mutter fails
building as per xvfb not able to run:
XIO: fatal IO error 88 (Socket operation on non-socket) on X server ":99"
after 209 requests (209 known processed) with 2 events remaining.
(EE) could not conne
Verified on a Kubuntu Focus M1 running focal:
erich@erich-KFocus:~$ apt-cache policy nvidia-settings
nvidia-settings:
Installed: 460.39-0ubuntu0.20.04.1
Candidate: 460.39-0ubuntu0.20.04.1
Version table:
*** 460.39-0ubuntu0.20.04.1 100
100 /var/lib/dpkg/status
Works exactly as expec
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
** Summary changed:
- xvfb fails when building mutter in hirsute-proposed
+ mutter fails to run using wayland with glib2.0 2.67.4-1
** Description changed:
When hirsute-proposed is enabled (works fine in hirsute), mutter fails
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2332
https://gitlab.gnome.org/GNOME/glib/-/issues/2332
** Also affects: xorg-server via
https://gitlab.gnome.org/GNOME/glib/-/issues/2332
Importance: Unknown
Status: Unknown
** Changed in: glib2.0 (Ubuntu)
Status: Ne
*** This bug is a duplicate of bug 1916701 ***
https://bugs.launchpad.net/bugs/1916701
** This bug has been marked a duplicate of bug 1916701
[glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
eventually comes up without Wayland support (only Xorg sessions offered)
--
** Tags added: amdgpu
** Summary changed:
- Screen fails to wake up after sleep
+ [amdgpu] Screen fails to wake up after sleep
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1427
https://gitlab.freedesktop.org/drm/amd/-/issues
Please try a 5.10 kernel as well as a 5.4 kernel so we can get a better
idea of which versions are affected:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
** Tags added: amdgpu radeon
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- AMD. Extreme slowness in x
23 matches
Mail list logo
