惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

罗磊的独立博客
U
Unit 42
N
Netflix TechBlog - Medium
人人都是产品经理
人人都是产品经理
Hugging Face - Blog
Hugging Face - Blog
腾讯CDC
小众软件
小众软件
V
Visual Studio Blog
T
Tailwind CSS Blog
Engineering at Meta
Engineering at Meta
博客园 - 叶小钗
GbyAI
GbyAI
爱范儿
爱范儿
雷峰网
雷峰网
Microsoft Azure Blog
Microsoft Azure Blog
D
DataBreaches.Net
博客园_首页
D
Docker
A
About on SuperTechFans
G
Google Developers Blog
I
InfoQ
T
The Blog of Author Tim Ferriss
V
V2EX
博客园 - Franky

Bugs for Charles Green

Bug #1736011 “CRITICAL: Unable to create a DBus proxy for GnomeS...” : Bugs : gnome-session package : Ubuntu Bug #1723815 “Unable to show files on MTP connection” : Bugs : gvfs package : Ubuntu Bug #1672297 “gnome-shell uses lots of memory, and grows over ti...” : Bugs : GNOME Shell Bug #1309300 “Upgrade to Trusty ruined wireless connectivity " : Bugs : network-manager package : Ubuntu Bug #1282847 “desktop ui scale is huge even though the setting i... : Bugs : gtk+3.0 package : Ubuntu Bug #495981 “NM disconnects Wi-Fi every 2 minutes but iwconfig+d...” : Bugs : network-manager package : Ubuntu
Bug #1811023 “Xorg aborts with ../../../../dix/privates.c...
errors.ubunt · 2019-01-09 · via Bugs for Charles Green

I am using nvidia-driver-460 version 460.39-0ubuntu0.20.04.1.

    xserver-common version 2:1.20.9-2ubuntu1.2~20.04.1
    xserver-xephyr version 2:1.20.9-2ubuntu1.2~20.04.1
    xserver-xorg version 1:7.7+19ubuntu14
    xserver-xorg-core version 2:1.20.9-2ubuntu1.2~20.04.1

The GDM screen would only appear after typing Ctrl+Alt+F2 followed by Ctrl+Alt+F1.

The following seems to have fixed the issue for me, and the GDM screen now appears without having to resort to the above "trick".

 1. Edit the file /lib/udev/rules.d/61-gdm.rules.

    sudo nano /lib/udev/rules.d/61-gdm.rules

    The original file looks like this:

    # disable Wayland on Hi1710 chipsets
    ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
    # disable Wayland when using the proprietary nvidia driver
    DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

    Comment all of the lines as shown:

    # disable Wayland on Hi1710 chipsets
    # ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
    # disable Wayland when using the proprietary nvidia driver
    # DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

    Type Ctrl+X to exit, then Y, and then Enter to save the file.

 2. Ensure that the Wayland is not disabled in GDM.

    sudo nano /etc/gdm3/custom.conf

    Comment the "WaylandEnable" line, if it is not already commented, as shown:

    # WaylandEnable=false

    Type Ctrl+X to exit. If you made changes, type Y, and then Enter to save the file.

 3. Finally, reboot.

Explanation

The /lib/udev/rules.d/61-gdm.rules file is supposed to prevent GDM from displaying the Wayland session option when the NVIDIA proprietary drivers are installed, since NVIDIA does not support Wayland.

However, in Ubuntu 20.04, there seems to be another redundant mechanism or rule that also prevents GDM from displaying the Wayland session option. I suspect this, because even after making the above change, the Wayland session option is still not displayed in GDM. (Setting WaylandEnable=true in /etc/gdm3/custom.conf has no effect).

Therefore, I have a hunch that there are two conflicting rules, and disabling one of the rules (i.e. /lib/udev/rules.d/61-gdm.rules) seems to remove the conflict.

Here is the journalctl boot log before making the above changes. You can see there is an error loading the "fb" module.

/usr/lib/gdm3/gdm-x-session[964]: (II) Loading sub module "fb"
/usr/lib/gdm3/gdm-x-session[964]: (II) LoadModule: "fb"
/usr/lib/gdm3/gdm-x-session[964]: (II) Loading /usr/lib/xorg/modules/libfb.so
/usr/lib/gdm3/gdm-x-session[964]: (II) Module fb: vendor="X.Org Foundation"
/usr/lib/gdm3/gdm-x-session[964]: compiled for 1.20.9, module version = 1.0.0
/usr/lib/gdm3/gdm-x-session[964]: ABI class: X.Org ANSI C Emulation, version 0.4
/usr/lib/gdm3/gdm-x-session[964]: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
/usr/lib/gdm3/gdm-x-session[964]: (EE)
/usr/lib/gdm3/gdm-x-session[964]: (EE) Backtrace:
/usr/lib/gdm3/gdm-x-session[964]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55936e23a59c]
/usr/lib/gdm3/gdm-x-...