** Changed in: oem-priority
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/2034105
Title:
Cursor didn't show up in X session when output
Yes, a nvidia tracker is needed. There are some questions we need to
sync with nvidia.
The Xorg task is needed (for jammy) because the nvidia driver will check
the version of Xorg (need 1.21.1.4+) to turn-on some features.
--
You received this bug notification because you are a member of
Hi Daniel,
The fix for this issue not only requires xorg 1.21.1.4, but also a newer
version of the Nvidia driver. We have confirmed that the combination
that fixes this issue is (1) xorg 1.21.1.4 (from Kinetic) + (2) a
development version of the Nvidia driver, which is under NDA.
To be honest,
** Tags added: originate-from-2009792
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2009767
Title:
external HDMI monitor is laggy on NV reverse PRIME system
To manage notifications
** Tags added: originate-from-2003066 stella
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2009767
Title:
external HDMI monitor is laggy on NV reverse PRIME system
To manage
okay, I can confirmed it works with latest packages from Jammy.
In both 'Launch using Discrete Graphics Card' and
'__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia' cases.
But it doesn't work for firefox (mine is a snap version) so I think we
are good to close this or switch to
https://github.com/tseliot/nvidia-settings/pull/14 for nvidia-settings
UI.
--
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/1982472
Title:
Support A+N platform
To manage notifications
Installed a package from a PPA won't break the package upgrade.
As Timo uploads the package to Unstable.
If everything goes smoothly, the next version of xserver-xorg-video-amdgpu will
contain the patches and that version will overwrite mine from the PPA.
In short, an "apt upgrade" will
FWIK, there are many related packages need to modify together since it's
similar to an interface change.
It'll be more reasonable if we target to Jammy+.
The power-saving mode in Jammy is almost useless (but the nvidia-340, 390 may
still need it).
However, the 'power-saving' mode apply:
```
Hi Josh,
In my experience on this issue, there are at least two ways to reproduce this
issue.
1. fresh install.
2. enable "FRAMEBUFFER=y" in initramfs.
As lenovo z16 is an AMD platform, would you please try to upgrade all
packages to latest and try the package from the ppa of comment#62?
BTW,
The xserver-xorg-video-amdgpu patches #63~#66 don't need in focal
because only Stock Jammy default installation will be affect.
The same symptom can be reproduced in both Focal and Jammy with applying
"FRAMEBUFFER=y" and the xserver-xorg-video-amdgpu patchset don't help.
--
You received this
More precisely, it seems related to
FRAMEBUFFER=y in "conf-hooks.d/cryptsetup".
When I marked it as 'n', then issue is gone.
Need to figure it out what's it exactly causes.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
In Focal Stock Ubuntu, I confirmed if user installs "cryptsetup-
initramfs" on I+A platform with choosing display mode to "External
Only", the issue presents.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
comment#63-66 for xserver-xorg-video-amdgpu on Jammy.
For debian and KKK, do we plan those to be landed through stable
updates?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
** Patch added:
"0004-Do-not-consider-disabled-crtc-anymore-when-looking-f.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875015/+attachment/5601763/+files/0004-Do-not-consider-disabled-crtc-anymore-when-looking-f.debdiff
--
You received this bug notification because
** Patch added:
"0003-Prefer-crtc-of-primary-output-for-synchronization-wh.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875015/+attachment/5601762/+files/0003-Prefer-crtc-of-primary-output-for-synchronization-wh.debdiff
--
You received this bug notification because
** Patch added:
"0002-Use-randr_crtc_covering_drawable-used-in-modesetting.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875015/+attachment/5601761/+files/0002-Use-randr_crtc_covering_drawable-used-in-modesetting.debdiff
--
You received this bug notification because
** Patch added: "0001-amdgpu-fixup-driver-for-new-X-server-ABI.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875015/+attachment/5601760/+files/0001-amdgpu-fixup-driver-for-new-X-server-ABI.debdiff
--
You received this bug notification because you are a member of
I can confirmed the commits from
https://gitlab.freedesktop.org/xorg/driver/xf86-video-
amdgpu/-/merge_requests/75/commits fix my issue on I+A machine using
Jammy and KKK daily build.
Test PPA is https://launchpad.net/~os369510/+archive/ubuntu/lp1875015
For Focal, it seems the extra patches are
** Attachment added: "/var/log/installer/syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1961375/+attachment/5561732/+files/syslog
** Description changed:
Using Jammy daily build 2022-02-02 on I+N desktop.
Boot_vga is dGPU (nvidia) with RTD3 supports.
+ Installation from
Public bug reported:
Using Jammy daily build 2022-02-02 on I+N desktop.
Boot_vga is dGPU (nvidia) with RTD3 supports.
Installation from USB without connecting network.
Feb 18 05:26:52 ubuntu ubiquity: Unpacking nvidia-settings (470.57.01-0ubuntu3)
...#015
Feb 18 05:26:52 ubuntu
ffects: oem-priority
Importance: Low
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: nvidia-settings (Ubuntu)
Importance: Undecided
Assignee: jeremyszu (os369510)
Status: New
** Tags: oem-priority
** Changed in: nvidia-settings (Ubuntu)
A
Hi Robie,
I'm apologize to missed this information.
I've add them in the bug description.
** Description changed:
+ [Impact]
+
+ * In any Ubuntu series, if user using a old GPU (which supported by
+ nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB
+ GLX visual or
nvidia-settings for focal
** Patch added: "18-lp1957094-adjust-on-demand-mode-description.focal.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554942/+files/18-lp1957094-adjust-on-demand-mode-description.focal.patch
--
You received this bug
ubuntu-drivers-common for focal
** Patch added:
"0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.focal.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554941/+files/0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.focal.patch
--
skip debdiff for jammy
--
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/1957094
Title:
on-demand mode doesn't work with nvidia-390
To manage notifications about this bug go to:
ubuntu-drivers-common for impish
** Patch added:
"0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554940/+files/0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.patch
--
You
nvidia-settings for impish
** Patch added: "18-lp1957094-adjust-on-demand-mode-description.patch"
https://bugs.launchpad.net/oem-priority/+bug/1957094/+attachment/5554939/+files/18-lp1957094-adjust-on-demand-mode-description.patch
** Also affects: nvidia-settings (Ubuntu)
Importance:
Hi Sponsors,
Would you please help to review this minor patch? thanks!
** Changed in: oem-priority
Status: In Progress => Triaged
** Summary changed:
- iris driver doesn't load correctly
+ iris driver doesn't load correctly on intel pci_id 0x4688
--
You received this bug notification
Impish and Jammy all have this patch.
We don't need to bother them.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1955566
Title:
iris driver doesn't load correctly on intel pci_id 0x4688
To
for focal
** Patch added: "mesa_21.0.3-0ubuntu0.3~20.04.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1955566/+attachment/5549109/+files/mesa_21.0.3-0ubuntu0.3~20.04.6.debdiff
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Ch
** Description changed:
[Impact]
- * iris driver doesn't load with pci_id 4688. Instead, it uses llvm.
- we expect the Intel GPU uses iris driver.
+ * iris driver doesn't load with pci_id 4688. Instead, it uses llvm.
+ we expect the Intel GPU uses iris driver.
[Test Plan]
-
Public bug reported:
[Impact]
* iris driver doesn't load with pci_id 4688. Instead, it uses llvm.
we expect the Intel GPU uses iris driver.
[Test Plan]
* $ DISPLAY=:0 glxinfo | grep -i opengl
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits)
...
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1875015
Title:
Ubuntu 20.04 and Displaylink is extremely slow
To
** Changed in: oem-priority
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg crashed with SIGABRT when under memory pressure
To manage
** Summary changed:
- The image is distrorted while use iGPU rendering and output via AMD GPU
+ The image is distorted while use iGPU rendering and output via AMD GPU
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
@Shengyao,
I meant the -dri1.
I think the -dri2 is backported from
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11877#.
Let's discuss it on upstream thread.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
I did submit a discussion to discuss about "Launch using Dedicated Graphic
Card" design.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4509
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4509
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4509
--
You received
@Shengyao,
We still can reproduce this issue by following:
1. boot from dGPU (AMD)
2. DRI_PRIME=1 gxlgear
3. resize the window slowly.
** Tags added: fossa-edge-staging
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
@Shengyao,
Thanks, would you please share the ppa you tested here that we could
give it a try?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1937988
Title:
The image is distrorted while use
Public bug reported:
[Steps to reproduce]
1. Connect a monitor on the AMD GPU.
2. Power on the system and boot into OS.
3. Run below command to launch glxgear
Cmd> DRI_PRIME=1 glxgears -info
[Expected result]
The image is not distrorted while running the glxgears
[Actual result]
The image is
** Changed in: oem-priority
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
To manage notifications about
** Tags added: originate-from-1932285
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
To manage notifications about this bug go to:
@Timo,
I guess you could get passed if adding "--oomable"
** Also affects: plainbox-provider-checkbox
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
```
Mar 3 18:07:02 kernel: [ 4935.420223] gnome-shell invoked oom-killer:
gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
Mar 3 18:07:16 kernel: [ 4949.440656] gnome-shell invoked oom-killer:
gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
Mar 3 18:08:11
** Tags added: originate-from-1929152 stella
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
To manage notifications about this bug go to:
** Changed in: oem-priority
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1923153
Title:
[radeon] Display output laggy from iGPU when operating
Hi Daniel,
Thank you for sharing.
We are not allow to provide a customization as workaround before we know the
fix plan.
I reported an upstream issue:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194
--
You received this bug notification because you are a member of
Hi Daniel,
Thank you for sharing.
OEM team is not allow the provide a customization as workaround before we don't
know the plan to fix.
I reported an issue as
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194
** Bug watch added:
@Daniel,
u@u-HP-EliteDesk-800-G6-Tower-PC:~$ dpkg -S
/usr/share/X11/xorg.conf.d/10-radeon.conf
xserver-xorg-video-radeon: /usr/share/X11/xorg.conf.d/10-radeon.conf
u@u-HP-EliteDesk-800-G6-Tower-PC:~$ dpkg -S
/usr/share/X11/xorg.conf.d/10-amdgpu.conf
xserver-xorg-video-amdgpu:
Hi Daniel,
Thanks for sharing comment#27.
Let me summarize the reproduce scenarios in Intel + AMD case.
1. Boot from iGPU -> switch to dGPU -> switch back to iGPU -> iGPU lag.
2. Boot from iGPU -> connect secondary monitor to dGPU -> remove 1st monitor
from iGPU -> dGPU lag.
3. Boot from iGPU
** Changed in: oem-priority
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1923153
Title:
[radeon] Display output laggy from iGPU when operating
Hi Daniel,
I could reproduce this issue when using today hirsute daily build
$ sha256sum ~/Downloads/hirsute-desktop-amd64.iso
4908a5c919f4b796a856be69a044334eb1a910727180618348db0a8a1ef70360
/home/jeremysu/Downloads/hirsute-desktop-amd64.iso
after switching back to xorg (hirsute default
The other finding for comment#20.
If connecting two monitors then there is a way to reproduce it.
1. Set iGPU as primary monitor
2. Run an application from secondary display (dGPU) (e.g. glxgear)
3. Moving the application from secondary display (dGPU) to primary display
(iGPU) then the issue
BTW, for i915 case, it's not 100% reproduce if the boot-vga-device is
i915.
Which means in Intel + AMD platform.
Sometime the system laggy when output from dGPU (AMD 430).
Sometime the system laggy when output from iGPU (intel) AFTER switching the
monitor between dGPU and iGPU (e.g. boot vga:
Hi Daniel,
The "AMD R7 430" is the product name of the graphic card.
https://ssl.www8.hp.com/emea_africa/en/products/oas/product-detail.html?oid=26185185
I guess it's related to radeon driver since we could see this issue with
amd RX550 as well.
** Tags added: originate-from-1923120
** Tags
@Daniel,
Above are the outputs.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1923153
Title:
Display output laggy from iGPU when operating on desktop with
attaching AMD
** Attachment added: "lspci2.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486866/+files/lspci2.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
** Attachment added: "journal2.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486867/+files/journal2.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
here is the output
** Attachment added: "journal-b-k.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486865/+files/journal-b-k.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
XFCE has the same result.
I'm able to reproduce this issue on XFCE.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1923153
Title:
Display output laggy from iGPU when
@Daniel,
ok, let me try the other desktops.
BTW, the cursor moves smoothly but other operations laggy (e.g. move the
terminal window).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
backport the patches from
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/460 doesn't
help.
---
* d5016e5b61f96496f9b31d14eae16f5f0148b748 (HEAD ->
backport-7-patches-from-Łukasz-sync_present_to_slave_outputs) Remove unused
function ms_covering_xf86_crtc()
*
BTW, the FPS is 1.
$ DISPLAY=:0 glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
344 frames in 5.6 seconds = 61.884 FPS
5 frames in 5.0 seconds = 0.997 FPS
6 frames in 6.0 seconds = 1.002 FPS
6 frames in 6.0
** Attachment added: "xrandr-verbose"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5485957/+files/xrandr-verbose
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in
When I attached another monitor to dGPU (which means connecting monitor
to each iGPU and dGPU), then there is no problem.
--
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/1923153
Title:
Display
-1916427 stella
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of
erver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
** Affects: oem-priority
Importance: Critical
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: xorg (Ubuntu)
Public bug reported:
Steps to produce this issue:
1. Install hirsute daily build
(495fe189e32d873ba79d7753134c22353ea89e8e6d62498f6c825a5de6a8a4a7
*hirsute-desktop-amd64.iso) from https://cdimage.ubuntu.com/daily-live/current/
2. Attach an AMD R7 430 graphic as dGPU without connecting any
Hi All,
I'd confirmed this issue is be fixed by gdm3 3.36.3-0ubuntu0.20.04.1 and
passed the 30 times reboot stress test by using stress/reboot_30 from
checkbox.
The environment:
kernel: 5.4.0-47-generic
gdm3: 3.36.3-0ubuntu0.20.04.1
nvidia-driver-440: 440.100-0ubuntu0.20.04.1
GPU: VGA
** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407599/+files/gdm3_3.34.1-1ubuntu2.debdiff
** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff"
I'd confirmed the regression with enabling Wayland.
Due to nvidia-driver (nvidia-driver-440) disable wayland as default, I'll
separate the verification to two scenarios.
1. Make sure the new gdm3 fixes this issue.
2. Make sure the new gdm3 without the regression
** Changed in: oem-priority
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then
I'd updated the debdiff to insert a DEP-3 header.
Here is the new debdiff.
** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5406013/+files/gdm3_3.34.1-1ubuntu2.debdiff
** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff"
[Summary]
Here are two scenario of auto login with groovy (20.10) daily build[1]:
1. Checked "Install third-party software" (e.g. nvidia-driver) with
enabling "Login automatically".
2. Install with default options
2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive.
2.2 Enable
[Summary]
Here are two scenario of auto login with groovy (20.10) daily build[1]:
1. Checked "Install third-party software" (e.g. nvidia-driver) with
enabling "Login automatically".
2. Install with default options
2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive.
2.2 Enable
Here is the debdiff.
** Patch added: "gdb3~oem-1891965.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5405674/+files/gdb3~oem-1891965.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
[Summary]
Here are two scenario of auto login with groovy (20.10) daily build[1]:
1. Checked "Install third-party software" (e.g. nvidia-driver) with
enabling "Login automatically".
2. Install with default options
2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive.
2.2 Enable
** Changed in: oem-priority
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all
I tried to install stock 20.04.1 ubuntu with 'Install third party pkgs
(e.g. nvidia)' + enable login automatically. After a reboot because of
installation completed, the system will stuck in GDM login screen and
can't login even if typing correct password.
--
You received this bug notification
Update for summarizing current symptoms and workaround solution:
[Steps to reproduce]
1. Enable auto login through GUI ("Settings"->"Users"->"Automatic Login" to
enable)
2. reboot
3. system stop at gdm login screen
There are two symptom I found currently:
4.1 enter correct password is not able
81 matches
Mail list logo
