我每天都得到相同的 Ubuntu 基础和台面更新。我现在已经安装了 10 多次相同的更新，并且每天它都会向我显示需要安装的相同更新。我不知道是什么导致了这个问题，同样我不知道我需要提供什么数据才能找到解决方案。

$ sudo apt update
Hit:1 http://ro-mirrors.evowise.com/ubuntu groovy InRelease
Hit:2 http://ro-mirrors.evowise.com/ubuntu groovy-updates InRelease              
Hit:3 http://ro-mirrors.evowise.com/ubuntu groovy-backports InRelease                                  
Hit:4 http://ro-mirrors.evowise.com/ubuntu groovy-security InRelease                                   
Hit:5 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu groovy InRelease                               
Hit:6 http://ppa.launchpad.net/lutris-team/lutris/ubuntu groovy InRelease                                                                  
Hit:7 https://dl.winehq.org/wine-builds/ubuntu groovy InRelease                                                                            
Hit:8 http://archive.canonical.com/ubuntu groovy InRelease                                                                                 
Get:9 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy InRelease [23.9 kB]                                    
Hit:10 https://deb.torproject.org/torproject.org groovy InRelease                                    
Fetched 23.9 kB in 2s (12.1 kB/s)                         
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://deb.torproject.org/torproject.org groovy InRelease' doesn't support architecture 'i386'

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ sudo apt dist-upgrade --dry-run**
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

更新可用后输入命令：

$ sudo apt update
Hit:1 http://ro-mirrors.evowise.com/ubuntu groovy InRelease
Hit:2 http://ro-mirrors.evowise.com/ubuntu groovy-updates InRelease                                                                        
Hit:3 http://ro-mirrors.evowise.com/ubuntu groovy-backports InRelease                                                                      
Hit:4 http://ro-mirrors.evowise.com/ubuntu groovy-security InRelease                                                                       
Hit:5 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu groovy InRelease                                                                
Get:6 https://dl.winehq.org/wine-builds/ubuntu groovy InRelease [6,259 B]                                                                  
Hit:7 http://archive.canonical.com/ubuntu groovy InRelease                                                                                 
Hit:8 http://ppa.launchpad.net/lutris-team/lutris/ubuntu groovy InRelease                                                   
Hit:9 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy InRelease
Hit:10 https://deb.torproject.org/torproject.org groovy InRelease        
Get:11 https://dl.winehq.org/wine-builds/ubuntu groovy/main Sources [2,416 B]
Get:12 https://dl.winehq.org/wine-builds/ubuntu groovy/main i386 Packages [11.4 kB]
Get:12 https://dl.winehq.org/wine-builds/ubuntu groovy/main i386 Packages [11.4 kB]
Err:12 https://dl.winehq.org/wine-builds/ubuntu groovy/main i386 Packages
  File has unexpected size (8364 != 11408). Mirror sync in progress? [IP: 151.101.10.217 443]
  Hashes of expected file:
   - Filesize:11408 [weak]
   - SHA512:0e20248f05259b4d3ead9506673eddf9718c92ff000274a944c278c58d8824d0702c1d31e71cb2eaacf6753b9900b1ef93bc6f969f8d85403f78e9ddccd478f9
   - SHA256:ef16c559a95c24229d151011d21379757819eedca7dc823c0149858bf0bc90fc
   - SHA1:883e373057f2e8cbaef410a8ba8b6180632d4496 [weak]
   - MD5Sum:53d09c898744d076aa509e04fb92aca2 [weak]
  Release file created at: Sat, 07 Nov 2020 15:59:19 +0000
Reading package lists... Done  
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://deb.torproject.org/torproject.org groovy InRelease' doesn't support architecture 'i386'
E: Failed to fetch https://dl.winehq.org/wine-builds/ubuntu/dists/groovy/main/binary-i386/Packages.xz  File has unexpected size (8364 != 11408). Mirror sync in progress? [IP: 151.101.10.217 443]
   Hashes of expected file:
    - Filesize:11408 [weak]
    - SHA512:0e20248f05259b4d3ead9506673eddf9718c92ff000274a944c278c58d8824d0702c1d31e71cb2eaacf6753b9900b1ef93bc6f969f8d85403f78e9ddccd478f9
    - SHA256:ef16c559a95c24229d151011d21379757819eedca7dc823c0149858bf0bc90fc
    - SHA1:883e373057f2e8cbaef410a8ba8b6180632d4496 [weak]
    - MD5Sum:53d09c898744d076aa509e04fb92aca2 [weak]
   Release file created at: Sat, 07 Nov 2020 15:59:19 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libegl-mesa0 libgbm1 libgbm1:i386 libgl1-mesa-dri libgl1-mesa-dri:i386 libgl1-mesa-glx libgl1-mesa-glx:i386 libglapi-mesa
  libglapi-mesa:i386 libglx-mesa0 libglx-mesa0:i386 libosmesa6 libosmesa6:i386 mesa-va-drivers mesa-va-drivers:i386 mesa-vdpau-drivers
  mesa-vdpau-drivers:i386 mesa-vulkan-drivers mesa-vulkan-drivers:i386
19 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 44.7 MB of archives.
After this operation, 4,096 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 libegl-mesa0 amd64 20.3~git2011070730.b7793e~oibaf~g [141 kB]
Get:2 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 libgbm1 i386 20.3~git2011070730.b7793e~oibaf~g [73.3 kB]
Get:3 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 libgbm1 amd64 20.3~git2011070730.b7793e~oibaf~g [72.2 kB]
Get:4 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 libgl1-mesa-dri amd64 20.3~git2011070730.b7793e~oibaf~g [10.1 MB]
Get:5 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 libgl1-mesa-dri i386 20.3~git2011070730.b7793e~oibaf~g [10.1 MB]
Get:6 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 libosmesa6 amd64 20.3~git2011070730.b7793e~oibaf~g [2,875 kB]
Get:7 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 libosmesa6 i386 20.3~git2011070730.b7793e~oibaf~g [2,888 kB] 
Get:8 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 libglx-mesa0 amd64 20.3~git2011070730.b7793e~oibaf~g [189 kB]
Get:9 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 libglx-mesa0 i386 20.3~git2011070730.b7793e~oibaf~g [197 kB] 
Get:10 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 libglapi-mesa i386 20.3~git2011070730.b7793e~oibaf~g [71.2 kB]
Get:11 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 libglapi-mesa amd64 20.3~git2011070730.b7793e~oibaf~g [71.1 kB]
Get:12 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 libgl1-mesa-glx amd64 20.3~git2011070730.b7793e~oibaf~g [50.6 kB]
Get:13 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 libgl1-mesa-glx i386 20.3~git2011070730.b7793e~oibaf~g [50.6 kB]
Get:14 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 mesa-va-drivers i386 20.3~git2011070730.b7793e~oibaf~g [2,755 kB]
Get:15 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 mesa-va-drivers amd64 20.3~git2011070730.b7793e~oibaf~g [2,668 kB]
Get:16 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 mesa-vdpau-drivers i386 20.3~git2011070730.b7793e~oibaf~g [2,884 kB]
Get:17 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 mesa-vdpau-drivers amd64 20.3~git2011070730.b7793e~oibaf~g [2,797 kB]
Get:18 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main i386 mesa-vulkan-drivers i386 20.3~git2011070730.b7793e~oibaf~g [3,366 kB]
Get:19 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu groovy/main amd64 mesa-vulkan-drivers amd64 20.3~git2011070730.b7793e~oibaf~g [3,362 kB]
Fetched 44.7 MB in 4min 10s (179 kB/s)                                                                                                     
(Reading database ... 212550 files and directories currently installed.)
Preparing to unpack .../00-libegl-mesa0_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
Unpacking libegl-mesa0:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../01-libgbm1_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
De-configuring libgbm1:i386 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking libgbm1:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../02-libgbm1_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
Unpacking libgbm1:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../03-libgl1-mesa-dri_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
De-configuring libgl1-mesa-dri:amd64 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking libgl1-mesa-dri:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../04-libgl1-mesa-dri_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
Unpacking libgl1-mesa-dri:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../05-libosmesa6_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
De-configuring libosmesa6:amd64 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking libosmesa6:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../06-libosmesa6_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
Unpacking libosmesa6:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../07-libglx-mesa0_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
De-configuring libglx-mesa0:amd64 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking libglx-mesa0:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../08-libglx-mesa0_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
Unpacking libglx-mesa0:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../09-libglapi-mesa_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
De-configuring libglapi-mesa:i386 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking libglapi-mesa:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../10-libglapi-mesa_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
Unpacking libglapi-mesa:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../11-libgl1-mesa-glx_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
De-configuring libgl1-mesa-glx:amd64 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking libgl1-mesa-glx:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../12-libgl1-mesa-glx_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
Unpacking libgl1-mesa-glx:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../13-mesa-va-drivers_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
De-configuring mesa-va-drivers:amd64 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking mesa-va-drivers:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../14-mesa-va-drivers_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
Unpacking mesa-va-drivers:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../15-mesa-vdpau-drivers_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
De-configuring mesa-vdpau-drivers:amd64 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking mesa-vdpau-drivers:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../16-mesa-vdpau-drivers_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
Unpacking mesa-vdpau-drivers:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../17-mesa-vulkan-drivers_20.3~git2011070730.b7793e~oibaf~g_i386.deb ...
De-configuring mesa-vulkan-drivers:amd64 (20.3~git2011061930.a0b42d~oibaf~g) ...
Unpacking mesa-vulkan-drivers:i386 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Preparing to unpack .../18-mesa-vulkan-drivers_20.3~git2011070730.b7793e~oibaf~g_amd64.deb ...
Unpacking mesa-vulkan-drivers:amd64 (20.3~git2011070730.b7793e~oibaf~g) over (20.3~git2011061930.a0b42d~oibaf~g) ...
Setting up mesa-vulkan-drivers:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up mesa-vulkan-drivers:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up mesa-vdpau-drivers:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up mesa-vdpau-drivers:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libgbm1:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libgbm1:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libglapi-mesa:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libglapi-mesa:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up mesa-va-drivers:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up mesa-va-drivers:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libosmesa6:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libosmesa6:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libgl1-mesa-dri:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libgl1-mesa-dri:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libegl-mesa0:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libglx-mesa0:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libglx-mesa0:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libgl1-mesa-glx:amd64 (20.3~git2011070730.b7793e~oibaf~g) ...
Setting up libgl1-mesa-glx:i386 (20.3~git2011070730.b7793e~oibaf~g) ...
Processing triggers for libc-bin (2.32-0ubuntu3) ...

我最近从 Ubuntu 18.04 LTS 升级到 20.04 LTS。

我注意到每当我玩游戏时，比如使用质子的杀手 2 或其他东西，它会在 30 分钟到 1 小时后冻结。这在 18.04 LTS 上从未发生过。

我注意到包无法升级，包括 libsane1、libsane-common 并且似乎卡在 18.04 LTS 版本中。（见下面的截图）如果我尝试更新它，它想删除 ubuntu-desktop 和其他 ubuntu 核心包。

我还注意到 libgl1-mesa-glx（以及我为玩游戏而安装的其他库）仍在 20.2.1~kisak1~b 上，据此它是仿生 18.04 LTS 版本。https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa/+build/20149684

我怀疑有些软件包在升级过程中没有升级到 20.04 LTS，我不知道如何修复它。

这是我的 journalctl -b -e 输出

11 月 5 日 18:28:43 hackintosh 跟踪器商店 [3289]：好的
11 月 5 日 18:28:43 hackintosh systemd [1677]：tracker-store.service：成功。
11 月 5 日 18:28:53 hackintosh nm-applet [2502]：gtk_widget_destroy：断言 'GTK_>
11 月 5 日 18:28:53 hackintosh nm-applet [2502]：gtk_widget_destroy：断言 'GTK_>
11 月 5 日 18:28:53 hackintosh nm-applet[2488]：gtk_widget_destroy：断言 'GTK_>
11 月 5 日 18:28:53 hackintosh nm-applet[2488]：gtk_widget_destroy：断言 'GTK_>
11 月 5 日 18:28:53 hackintosh nm-applet [2502]：无法在小部件上设置父级 >
11 月 5 日 18:28:53 hackintosh nm-applet [2488]：无法在小部件上设置父级 >
11 月 5 日 18:28:56 hackintosh systemd-resolved[912]：服务器返回错误 NXDOMAI>
11 月 5 日 18:29:11 hackintosh dbus-daemon[1720]: [session uid=1000 pid=1720] Activ>
11 月 5 日 18:29:11 hackintosh systemd[1677]：创建切片 apps.slice。
11 月 5 日 18:29:11 hackintosh systemd [1677]：创建切片 apps-org.gnome.Terminal>
11 月 5 日 18:29:11 hackintosh systemd [1677]：正在启动 GNOME 终端服务器...
11 月 5 日 18:29:11 hackintosh dbus-daemon [1720]：[会话 uid=1000 pid=1720] 成功>
11 月 5 日 18:29:11 hackintosh systemd [1677]：启动 GNOME 终端服务器。
11 月 5 日 18:29:11 hackintosh gnome-terminal-server [3781]：Fontconfig 警告：“/e>
11 月 5 日 18:29:11 hackintosh gnome-terminal-server [3781]：Fontconfig 警告：“/e>
11 月 5 日 18:29:11 hackintosh systemd [1677]：启动 VTE 子进程 3789 启动>
11 月 5 日 18:29:27 hackintosh systemd-resolved[912]：服务器返回错误 NXDOMAI>
11 月 5 日 18:29:29 hackintosh sudo [3823]: pam_unix(sudo:auth): 无法打开 /etc/>
11 月 5 日 18:29:31 hackintosh sudo [3823]: pam_unix(sudo:auth): 无法打开 /etc/>
11 月 5 日 18:29:31 hackintosh sudo[3823]: cley : TTY=pts/1 ; 密码=/家/克莱；>
11 月 5 日 18:29:31 hackintosh sudo [3823]: pam_unix(sudo:session): 会话打开 f>
第 979-1001/1001 行（完）
11 月 5 日 18:28:43 hackintosh 跟踪器商店 [3289]：好的
11 月 5 日 18:28:43 hackintosh systemd [1677]：tracker-store.service：成功。
11 月 5 日 18:28:53 hackintosh nm-applet[2502]: gtk_widget_destroy: 断言 'GTK_IS_WIDGET (widget)' 失败
11 月 5 日 18:28:53 hackintosh nm-applet[2502]: gtk_widget_destroy: 断言 'GTK_IS_WIDGET (widget)' 失败
11 月 5 日 18:28:53 hackintosh nm-applet[2488]：gtk_widget_destroy：断言“GTK_IS_WIDGET（小部件）”失败
11 月 5 日 18:28:53 hackintosh nm-applet[2488]：gtk_widget_destroy：断言“GTK_IS_WIDGET（小部件）”失败
11 月 5 日 18:28:53 hackintosh nm-applet [2502]：无法在具有父级的小部件上设置父级
11 月 5 日 18:28:53 hackintosh nm-applet [2488]：无法在具有父级的小部件上设置父级
11 月 5 日 18:28:56 hackintosh systemd-resolved[912]：服务器返回错误 NXDOMAIN，缓解潜在的 DNS 违规 DVE-2018-0001，使用降低的功能级别 UDP 重试事务。
11 月 5 日 18:29:11 hackintosh dbus-daemon[1720]: [session uid=1000 pid=1720] 通过 systemd 激活：服务名称='org.gnome.Terminal' unit='gnome-terminal-server.service' 请求通过'：1.118'（uid=1000 pid=3778 >
11 月 5 日 18:29:11 hackintosh systemd[1677]：创建切片 apps.slice。
11 月 5 日 18:29:11 hackintosh systemd[1677]：创建切片 apps-org.gnome.Terminal.slice。
11 月 5 日 18:29:11 hackintosh systemd [1677]：正在启动 GNOME 终端服务器...
11 月 5 日 18:29:11 hackintosh dbus-daemon[1720]: [session uid=1000 pid=1720] 成功激活服务 'org.gnome.Terminal'
11 月 5 日 18:29:11 hackintosh systemd [1677]：启动 GNOME 终端服务器。
11 月 5 日 18:29:11 hackintosh gnome-terminal-server[3781]：Fontconfig 警告：“/etc/fonts/conf.avail/65-ttf-droid-sans-fonts.conf”，第 61 行：有多个值不受支持，可能无法作为 ex>
11 月 5 日 18:29:11 hackintosh gnome-terminal-server[3781]：Fontconfig 警告：“/etc/fonts/conf.avail/65-ttf-droid-sans-fonts.conf”，第 96 行：有多个值不受支持，可能无法作为 ex>
11 月 5 日 18:29:11 hackintosh systemd [1677]：启动了由 gnome-terminal-server 进程 3781 启动的 VTE 子进程 3789。
11 月 5 日 18:29:27 hackintosh systemd-resolved[912]：服务器返回错误 NXDOMAIN，缓解潜在的 DNS 违规 DVE-2018-0001，使用降低的功能级别 UDP 重试事务。
11 月 5 日 18:29:29 hackintosh sudo [3823]：pam_unix(sudo:auth)：无法打开 /etc/securetty：没有这样的文件或目录
11 月 5 日 18:29:31 hackintosh sudo [3823]：pam_unix(sudo:auth)：无法打开 /etc/securetty：没有这样的文件或目录
11 月 5 日 18:29:31 hackintosh sudo[3823]: cley : TTY=pts/1 ; 密码=/家/克莱；用户=根；命令=/bin/journalctl -b -e
11 月 5 日 18:29:31 hackintosh sudo [3823]: pam_unix(sudo:session): 会话由 (uid=0) 为用户 root 打开

***编辑

我注意到我的发行版升级可能已损坏

这是我的 apt.log

记录时间：2020-11-05 18:37:31.210246
启动 pkgProblemResolver 时计数中断：1
启动 2 pkgProblemResolver，计数中断：1
调查 (0) libsensors-config:amd64 1:3.6.0-2ubuntu1 @in uN Ib >
损坏的 libsensors-config:amd64 libsensors4:amd64 上的冲突
  考虑 libsensors4:amd64 6 作为 libsensors-config:amd64 0 的解决方案
  保留 libsensors-config:amd64 而不是更改 libsensors4:amd64
调查 (1) libsensors5:amd64 1:3.6.0-2ubuntu1 @un uN Ib >
损坏的 libsensors5:amd64 取决于 libsensors-config:amd64
  考虑 libsensors-config:amd64 0 作为 libsensors5:amd64 0 的解决方案
  保留 libsensors5:amd64 而不是更改 libsensors-config:amd64
调查 (2) libsnmp35:amd64 5.8+dfsg-2ubuntu2.3 @un uN Ib >
损坏的 libsnmp35:amd64 取决于 libsensors5:amd64 (>= 1:3.5.0)
  考虑 libsensors5:amd64 0 作为 libsnmp35:amd64 3 的解决方案
  保留 libsnmp35:amd64 而不是更改 libsensors5:amd64
调查 (3) libsane:amd64 1.0.29-0ubuntu5.2 @un uN Ib >
损坏的 libsane:amd64 取决于 libsnmp35:amd64 (>= 5.8+dfsg)
  考虑 libsnmp35:amd64 3 作为 libsane:amd64 10 的解决方案
  保留 libsane:amd64 而不是更改 libsnmp35:amd64
调查 (3) sane-utils:amd64 1.0.29-0ubuntu5.2 @un uN Ib >
损坏的 sane-utils:amd64 取决于 libsane:amd64 (>= 1.0.27)
  考虑 libsane:amd64 10 作为 sane-utils:amd64 3 的解决方案
  阻止 sane-utils:amd64 而不是更改 libsane:amd64
调查 (3) libsane1:amd64 1.0.29-0ubuntu5.2 @ii umU NPb Ib >
损坏的 libsane1:amd64 取决于 libsane:amd64 (>= 1.0.29-0ubuntu5.2)
  考虑 libsane:amd64 10 作为 libsane1:amd64 0 的解决方案
  删除 libsane1:amd64 而不是更改 libsane:amd64
调查（4）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 10 作为 colord:amd64 42 的解决方案
  将 libsane:amd64 添加到删除列表
  通过保持 libsane:amd64 修复 colord:amd64
调查（5）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 42 作为 colord:amd64 42 的解决方案
  删除 colord:amd64 而不是更改 libsane:amd64
调查 (6) gnome-control-center:amd64
损坏的 gnome-control-center:amd64 取决于 colord:amd64 (>= 0.1.30)
  考虑 colord:amd64 42 作为 gnome-control-center:amd64 54 的解决方案
  将 colord:amd64 添加到删除列表
  通过保持 colord:amd64 修复 gnome-control-center:amd64
调查（6）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 42 作为 colord:amd64 54 的解决方案
  将 libsane:amd64 添加到删除列表
  通过保持 libsane:amd64 修复 colord:amd64
调查（7）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 54 作为 colord:amd64 54 的解决方案
  删除 colord:amd64 而不是更改 libsane:amd64
调查 (8) gnome-control-center:amd64
损坏的 gnome-control-center:amd64 取决于 colord:amd64 (>= 0.1.30)
  考虑 colord:amd64 54 作为 gnome-control-center:amd64 54 的解决方案
  删除 gnome-control-center:amd64 而不是更改 colord:amd64
调查 (8) ubuntu-desktop-minimal:amd64
损坏的 ubuntu-desktop-minimal:amd64 取决于 gnome-control-center:amd64
  考虑 gnome-control-center:amd64 54 作为 ubuntu-desktop-minimal:amd64 1 的解决方案
  删除 ubuntu-desktop-minimal:amd64 而不是更改 gnome-control-center:amd64
调查 (8) ubuntu-desktop:amd64
损坏的 ubuntu-desktop:amd64 取决于 gnome-control-center:amd64
  考虑 gnome-control-center:amd64 54 作为 ubuntu-desktop:amd64 0 的解决方案
  删除 ubuntu-desktop:amd64 而不是更改 gnome-control-center:amd64
完毕
ERROR:root:Package brscan4 没有设置优先级
ERROR:root:Package mfcj480dwlpr:i386 has no priority set
ERROR:root:Package minecraft-launcher 没有设置优先级
错误：root：NvidiaDetection 返回一个错误：int() 的无效文字，基数为 10：'server'
启动 pkgProblemResolver 时计数中断：1
启动 2 pkgProblemResolver，计数中断：1
调查 (0) ubuntu-desktop:amd64
损坏的 ubuntu-desktop:amd64 取决于 gnome-control-center:amd64
  考虑 gnome-control-center:amd64 7 作为 ubuntu-desktop:amd64 10000 的解决方案
  将 gnome-control-center:amd64 添加到删除列表
损坏的 ubuntu-desktop:amd64 取决于 ubuntu-desktop-minimal:amd64
  考虑 ubuntu-desktop-minimal:amd64 1 作为 ubuntu-desktop:amd64 10000 的解决方案
  将 ubuntu-desktop-minimal:amd64 添加到删除列表
  通过保持 gnome-control-center:amd64 修复 ubuntu-desktop:amd64
  通过保留 ubuntu-desktop-minimal:amd64 修复 ubuntu-desktop:amd64
调查 (0) gnome-control-center:amd64
损坏的 gnome-control-center:amd64 取决于 colord:amd64 (>= 0.1.30)
  考虑 colord:amd64 5 作为 gnome-control-center:amd64 7 的解决方案
  将 colord:amd64 添加到删除列表
  通过保持 colord:amd64 修复 gnome-control-center:amd64
调查 (0) 有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 0 作为 colord:amd64 5 的解决方案
  将 libsane:amd64 添加到删除列表
  通过保持 libsane:amd64 修复 colord:amd64
调查（1）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 0 作为 colord:amd64 5 的解决方案
  将 libsane:amd64 添加到删除列表
  通过保持 libsane:amd64 修复 colord:amd64
调查（2）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 0 作为 colord:amd64 5 的解决方案
  将 libsane:amd64 添加到删除列表
  通过保持 libsane:amd64 修复 colord:amd64
调查（3）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 5 作为 colord:amd64 5 的解决方案
  删除 colord:amd64 而不是更改 libsane:amd64
调查 (4) gnome-control-center:amd64
损坏的 gnome-control-center:amd64 取决于 colord:amd64 (>= 0.1.30)
  考虑 colord:amd64 5 作为 gnome-control-center:amd64 7 的解决方案
  将 colord:amd64 添加到删除列表
  通过保持 colord:amd64 修复 gnome-control-center:amd64
调查（4）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 5 作为 colord:amd64 7 的解决方案
  将 libsane:amd64 添加到删除列表
  通过保持 libsane:amd64 修复 colord:amd64
调查（5）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 7 作为 colord:amd64 7 的解决方案
  删除 colord:amd64 而不是更改 libsane:amd64
调查 (6) gnome-control-center:amd64
损坏的 gnome-control-center:amd64 取决于 colord:amd64 (>= 0.1.30)
  考虑 colord:amd64 7 作为 gnome-control-center:amd64 7 的解决方案
  删除 gnome-control-center:amd64 而不是更改 colord:amd64
调查 (6) ubuntu-desktop-minimal:amd64
损坏的 ubuntu-desktop-minimal:amd64 取决于 gnome-control-center:amd64
  考虑 gnome-control-center:amd64 7 作为 ubuntu-desktop-minimal:amd64 1 的解决方案
  删除 ubuntu-desktop-minimal:amd64 而不是更改 gnome-control-center:amd64
调查 (7) ubuntu-desktop:amd64
损坏的 ubuntu-desktop:amd64 取决于 gnome-control-center:amd64
  考虑 gnome-control-center:amd64 7 作为 ubuntu-desktop:amd64 10000 的解决方案
  将 gnome-control-center:amd64 添加到删除列表
损坏的 ubuntu-desktop:amd64 取决于 ubuntu-desktop-minimal:amd64
  考虑 ubuntu-desktop-minimal:amd64 7 作为 ubuntu-desktop:amd64 10000 的解决方案
  将 ubuntu-desktop-minimal:amd64 添加到删除列表
  通过保持 gnome-control-center:amd64 修复 ubuntu-desktop:amd64
  通过保留 ubuntu-desktop-minimal:amd64 修复 ubuntu-desktop:amd64
调查 (7) gnome-control-center:amd64
损坏的 gnome-control-center:amd64 取决于 colord:amd64 (>= 0.1.30)
  考虑 colord:amd64 7 作为 gnome-control-center:amd64 10000 的解决方案
  将 colord:amd64 添加到删除列表
  通过保持 colord:amd64 修复 gnome-control-center:amd64
调查（7）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 7 作为 colord:amd64 10000 的解决方案
  将 libsane:amd64 添加到删除列表
  通过保持 libsane:amd64 修复 colord:amd64
调查（8）有色：amd64
破碎的颜色：amd64 取决于 libsane:amd64 (>= 1.0.24)
  考虑 libsane:amd64 10000 作为 colord:amd64 10000 的解决方案
  删除 colord:amd64 而不是更改 libsane:amd64
调查 (9) gnome-control-center:amd64
损坏的 gnome-control-center:amd64 取决于 colord:amd64 (>= 0.1.30)
  考虑 colord:amd64 10000 作为 gnome-control-center:amd64 10000 的解决方案
  删除 gnome-control-center:amd64 而不是更改 colord:amd64
调查 (9) ubuntu-desktop-minimal:amd64
损坏的 ubuntu-desktop-minimal:amd64 取决于 gnome-control-center:amd64
  考虑 gnome-control-center:amd64 10000 作为 ubuntu-desktop-minimal:amd64 10000 的解决方案
  删除 ubuntu-desktop-minimal:amd64 而不是更改 gnome-control-center:amd64
完毕
ERROR:root:failed to mark 'ubuntu-desktop' for install (E:Unable to correct questions, you have been broken packages.)

我正在尝试通过以下方式从 Ubuntu 18.04.5 升级到 20.04.1：

$ sudo do-release-upgrade

这失败如下：

...

无法计算升级

计算升级时出现无法解决的问题。

这可能是由以下原因引起的：
Ubuntu 未提供非官方软件包 请使用 ppa-purge 软件包中的“ppa-purge”工具从 Launchpad PPA 中删除软件并再次尝试升级。

如果以上都不适用，请在终端中使用命令“ubuntu-bug ubuntu-release-upgrader-core”报告此错误。如果您想自己调查此问题，“/var/log/dist-upgrade”中的日志文件将包含有关升级的详细信息。具体来说，查看“main.log”和“apt.log”。

的尾部/var/log/dist-upgrade/main.log包含以下错误：

...
2020-10-11 18:36:30,320 WARNING Can't mark 'ubuntu-desktop' for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.)
2020-10-11 18:36:31,747 ERROR Dist-upgrade failed: 'Broken packages after upgrade: colord'
2020-10-11 18:36:31,747 DEBUG abort called
2020-10-11 18:36:31,755 DEBUG openCache()
2020-10-11 18:36:37,070 DEBUG Comparing 4.15.0-117 with 
2020-10-11 18:36:37,071 DEBUG Comparing 4.15.0-118 with 4.15.0-117
2020-10-11 18:36:37,824 DEBUG /openCache(), new cache size 99980

以下是 的反向包依赖项colord：

$ apt-cache rdepends colord
colord
Reverse Depends:
  colord-sensor-argyll
  gnome-control-center
    colord:i386
  cups-filters
    colord:i386
  cups-daemon
    colord:i386
  cups
    colord:i386
  xiccd
    colord:i386
  krita
    colord:i386
  gnome-color-manager
    colord:i386
  foomatic-filters
    colord:i386
  dispcalgui
    colord:i386
  diffoscope
    colord:i386
  colord-sensor-argyll
    colord:i386
  colord-sensor-argyll
  colord-data
  colord-sensor-argyll
    colord:i386
  argyll
    colord:i386
  libcolord2
    colord:i386
  libcolord-gtk1
    colord:i386
  gnome-control-center
    colord:i386
  cups-filters
    colord:i386
  cups-daemon
    colord:i386
  cups
    colord:i386
  colord-data

我最近遇到了分段错误问题，mesa并从ppa:kisak/kisak-mesa. 这可能会导致现在的升级问题。

colord如果我删除包会发生以下情况：

$ sudo apt-get remove colord 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  apg colord-data gnome-control-center-faces gnome-online-accounts libcolorhug2 libnss-myhostname linux-headers-4.15.0-117 linux-headers-4.15.0-117-generic
  linux-image-4.15.0-117-generic linux-modules-4.15.0-117-generic linux-modules-extra-4.15.0-117-generic python3-macaroonbakery python3-nacl
  python3-protobuf python3-pymacaroons python3-rfc3339 ubuntu-system-service
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  colord gnome-control-center ubuntu-desktop
0 upgraded, 0 newly installed, 3 to remove and 8 not upgraded.
After this operation, 5,782 kB disk space will be freed.
Do you want to continue? [Y/n]

这听起来不是一个好主意，因为上次我删除ubuntu-desktopUI 时不再启动。请参阅链接的帖子。

问题

如何解决升级问题而不冒分段错误重生的风险？

有关的

• 包更新/台面分段错误后 Ubuntu 18.04.4 启动卡住
• 由于被保留的软件包，似乎无法从 18.04 升级到 20.04：libsensors4、libsensors-config、colord
• libsensors5 或 libsensors-config 升级问题
• 从 18.04 升级到 20.04 失败...

TL;博士

/usr/lib/gdm3/gdm-x-session[5106]: (EE) 地址 0x56131d0000f7 的分段错误

启动问题

我今天在我的机器上关闭了 Ubuntu 18.04.4，稍后再冷启动它。现在它开始但不再到达 UI 阶段。启动过程以屏幕上的以下输出结束（输出的尾部）：

...
[  OK  ] Started Hostname Service.
[  OK  ] Started Network Manager.
         Starting Network Manager Wait Online...
[  OK  ] Reached target Network.
         Starting Permit User Sessions...
         Starting OpenVPN service...
[  OK  ] Started Unattended Upgrades Shutdown.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started OpenVPN service.
         Starting Network Manager Script Dispatcher Service...
         Starting GNOME Display Manager...
         Starting hold until boot process finishes up...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started GNOME Display Manager.
[  OK  ] Started Disk Manager.
[  OK  ] Started LSB: Speech Dispatcher.
[  OK  ] Started LSB: Record successful boot for GRUB.
[  OK  ] Started LSB: automatic crash report generation.

注意：当我重新开始时，shell 输出的顺序会有所不同。

我唯一能做的就是按下POWER按钮。结果 Ubuntu 关闭了。

GRUB 和恢复模式

我在启动时按右键进入了 GRUB (2.02) SHIFT。

我正在使用 Linux 4.15.0.-112-generic。还有4.15.0.-111-generic, 4.2.0.-42-generic, 4.2.0.-41-generic, 3.13.0.-64-generic, ... 可用。

当我选择时4.15.0.-112-generic (recovery mode)，启动过程不会进一步。但我到了Recovery menu: filesystem state: read-only).

当我选择时，Resume normal boot我会进入通常的 UI 登录。

历史

我调查/var/log/apt/history.log并发现了这些：

Start-Date: 2020-08-03  19:33:21
Commandline: aptdaemon role='role-commit-packages' sender=':1.368'
Upgrade: 
libldap-2.4-2:amd64 (2.4.45+dfsg-1ubuntu1.5, 2.4.45+dfsg-1ubuntu1.6), 
slack-desktop:amd64 (4.7.0, 4.8.0), 
python3-distupgrade:amd64 (1:18.04.37, 1:18.04.38), 
ubuntu-release-upgrader-core:amd64 (1:18.04.37, 1:18.04.38), 
libldap-common:amd64 (2.4.45+dfsg-1ubuntu1.5, 2.4.45+dfsg-1ubuntu1.6), 
code:amd64 (1.47.0-1594283939, 1.47.3-1595520028), 
ubuntu-release-upgrader-gtk:amd64 (1:18.04.37, 1:18.04.38), 
mesa-vdpau-drivers:amd64 (19.2.8-0ubuntu0~18.04.3, 20.0.8-0ubuntu1~18.04.1), 
mesa-va-drivers:amd64 (19.2.8-0ubuntu0~18.04.3, 20.0.8-0ubuntu1~18.04.1)
End-Date: 2020-08-03  19:33:43

Start-Date: 2020-08-03  19:37:12
Commandline: aptdaemon role='role-commit-packages' sender=':1.368'
Upgrade: 
git-gui:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-man:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-svn:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-daemon-sysvinit:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1),
gitk:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
gitweb:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-mediawiki:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-email:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-all:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-cvs:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-doc:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1), 
git-el:amd64 (1:2.27.0-1~ppa0~ubuntu18.04.1, 1:2.28.0-0ppa1~ubuntu18.04.1)
End-Date: 2020-08-03  19:37:31

Start-Date: 2020-08-03  19:38:54
Commandline: aptdaemon role='role-commit-packages' sender=':1.368'
Upgrade: 
libegl1-mesa-dev:amd64 (19.2.8-0ubuntu0~18.04.3, 20.0.8-0ubuntu1~18.04.1), 
mesa-common-dev:amd64 (19.2.8-0ubuntu0~18.04.3, 20.0.8-0ubuntu1~18.04.1), 
cifs-utils:amd64 (2:6.8-1, 2:6.8-1ubuntu1)
End-Date: 2020-08-03  19:39:00

Start-Date: 2020-08-03  19:40:55
Commandline: aptdaemon role='role-commit-packages' sender=':1.368'
Upgrade: brave-browser:amd64 (1.10.97, 1.11.104)
End-Date: 2020-08-03  19:41:10

Start-Date: 2020-08-03  19:42:16
Commandline: aptdaemon role='role-commit-packages' sender=':1.368'
Upgrade: 
libglapi-mesa:amd64 (19.2.8-0ubuntu0~18.04.3, 20.0.8-0ubuntu1~18.04.1), 
libgl1-mesa-dri:amd64 (19.2.8-0ubuntu0~18.04.3, 20.0.8-0ubuntu1~18.04.1), 
libglx-mesa0:amd64 (19.2.8-0ubuntu0~18.04.3, 20.0.8-0ubuntu1~18.04.1)
End-Date: 2020-08-03  19:42:19

Start-Date: 2020-08-03  19:43:14
Commandline: aptdaemon role='role-commit-packages' sender=':1.368'
Upgrade: 
grub-common:amd64 (2.02-2ubuntu8.15, 2.02-2ubuntu8.17), 
grub2-common:amd64 (2.02-2ubuntu8.15, 2.02-2ubuntu8.17), 
grub-pc:amd64 (2.02-2ubuntu8.15, 2.02-2ubuntu8.17), 
grub-pc-bin:amd64 (2.02-2ubuntu8.15, 2.02-2ubuntu8.17)
End-Date: 2020-08-03  19:43:29

系统日志

我查看syslog并在那里发现了一个看起来可疑的分段错误：

...
Aug  4 18:07:47 COMP systemd[5094]: Reached target Basic System.
Aug  4 18:07:47 COMP systemd[1]: Started User Manager for UID 125.
Aug  4 18:07:47 COMP systemd[5094]: Reached target Default.
Aug  4 18:07:47 COMP systemd[5094]: Startup finished in 54ms.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (--) Log file renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-5108.log" to "/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: X.Org X Server 1.19.6
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Release Date: 2017-12-20
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: X Protocol Version 11, Revision 0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Current Operating System: Linux COMP 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=e15b2ef7-c32d-46f5-a3a8-4bdc60285b4e ro quiet splash vt.handoff=1
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Build Date: 03 June 2019  08:10:35AM
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see http://www.ubuntu.com/support)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Current version of pixman: 0.34.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Before reporting problems, check http://wiki.x.org
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011to make sure that you have the latest version.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Markers: (--) probed, (**) from config file, (==) default setting,
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011(++) from command line, (!!) notice, (II) informational,
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Log file: "/var/lib/gdm3/.local/share/xorg/Xorg.0.log", Time: Tue Aug  4 18:07:47 2020
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) No Layout section.  Using the first Screen section.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) No screen section available. Using defaults.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (**) |-->Screen "Default Screen Section" (0)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (**) |   |-->Monitor "<default monitor>"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) No monitor specified for screen "Default Screen Section".
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Using a default monitor configuration.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Automatically adding devices
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Automatically enabling devices
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Automatically adding GPU devices
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Automatically binding GPU devices
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Max clients allowed: 256, resource mask: 0x1fffff
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Entry deleted from font path.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Entry deleted from font path.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Entry deleted from font path.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Entry deleted from font path.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Entry deleted from font path.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) FontPath set to:
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011/usr/share/fonts/X11/misc,
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011/usr/share/fonts/X11/Type1,
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011built-ins
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) ModulePath set to "/usr/lib/xorg/modules"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) The server relies on udev to provide the list of input devices.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011If no devices become available, reconfigure udev or disable AutoAddDevices.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loader magic: 0x56131c3ef020
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Module ABI versions:
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011X.Org ANSI C Emulation: 0.4
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011X.Org Video Driver: 23.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011X.Org XInput driver : 24.1
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011X.Org Server Extension : 10.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (++) using VT number 1
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) systemd-logind: took control of session /org/freedesktop/login1/session/c94
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) xfree86: Adding drm device (/dev/dri/card0)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (--) PCI:*(0:0:2:0) 8086:2a42:17aa:2112 rev 7, Mem @ 0xf4400000/4194304, 0xd0000000/268435456, I/O @ 0x00001800/8, BIOS @ 0x????????/131072
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (--) PCI: (0:0:2:1) 8086:2a43:17aa:2112 rev 7, Mem @ 0xf4200000/1048576
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) LoadModule: "glx"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Module glx: vendor="X.Org Foundation"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011compiled for 1.19.6, module version = 1.0.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011ABI class: X.Org Server Extension, version 10.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Matched modesetting as autoconfigured driver 0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Matched fbdev as autoconfigured driver 1
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Matched vesa as autoconfigured driver 2
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) Assigned the driver to the xf86ConfigLayout
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) LoadModule: "modesetting"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Module modesetting: vendor="X.Org Foundation"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011compiled for 1.19.6, module version = 1.19.6
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Module class: X.Org Video Driver
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011ABI class: X.Org Video Driver, version 23.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) LoadModule: "fbdev"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Module fbdev: vendor="X.Org Foundation"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011compiled for 1.19.3, module version = 0.4.4
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Module class: X.Org Video Driver
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011ABI class: X.Org Video Driver, version 23.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) LoadModule: "vesa"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Module vesa: vendor="X.Org Foundation"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011compiled for 1.19.3, module version = 2.3.4
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011Module class: X.Org Video Driver
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011ABI class: X.Org Video Driver, version 23.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) FBDEV: driver for framebuffer: fbdev
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) VESA: driver for VESA chipsets: vesa
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) modeset(0): using drv /dev/dri/card0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (WW) Falling back to old probe method for fbdev
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loading sub module "fbdevhw"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) LoadModule: "fbdevhw"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Module fbdevhw: vendor="X.Org Foundation"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011compiled for 1.19.6, module version = 0.0.2
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011ABI class: X.Org Video Driver, version 23.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) open /dev/fb0: Permission denied
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (WW) Falling back to old probe method for vesa
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) modeset(0): Creating default Display subsection in Screen section
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011"Default Screen Section" for depth/fbbpp 24/32
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) modeset(0): Depth 24, (==) framebuffer bpp 32
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) modeset(0): RGB weight 888
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (==) modeset(0): Default visual is TrueColor
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loading sub module "glamoregl"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) LoadModule: "glamoregl"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) Module glamoregl: vendor="X.Org Foundation"
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011compiled for 1.19.6, module version = 1.0.0
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011ABI class: X.Org ANSI C Emulation, version 0.4
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (II) glamor: OpenGL accelerated X.org driver based.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) Backtrace:
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x56131c15fabd]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 1: /usr/lib/xorg/Xorg (0x56131bfa7000+0x1bc859) [0x56131c163859]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fdd821dc000+0x128a0) [0x7fdd821ee8a0]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 3: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7fdd7945c000+0x129cc) [0x7fdd7946e9cc]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 4: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7fdd7945c000+0x1b19e) [0x7fdd7947719e]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 5: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7fdd7945c000+0x216df) [0x7fdd7947d6df]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 6: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7fdd7945c000+0x1ac0b) [0x7fdd79476c0b]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 7: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7fdd7945c000+0x16b7d) [0x7fdd79472b7d]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 8: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7fdd7945c000+0x16bc5) [0x7fdd79472bc5]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 9: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7fdd7945c000+0x10948) [0x7fdd7946c948]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 10: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x10b) [0x7fdd7ea75c9b]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 11: /usr/lib/xorg/modules/drivers/modesetting_drv.so (0x7fdd7f2b3000+0x9dc9) [0x7fdd7f2bcdc9]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 12: /usr/lib/xorg/Xorg (InitOutput+0xc08) [0x56131c040288]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 13: /usr/lib/xorg/Xorg (0x56131bfa7000+0x56cd3) [0x56131bffdcd3]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7fdd81e0cb97]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) 15: /usr/lib/xorg/Xorg (_start+0x2a) [0x56131bfe7b8a]
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) Segmentation fault at address 0x56131d0000f7
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Fatal server error:
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: Please consult the The X.Org Foundation support
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: #011 at http://wiki.x.org
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]:  for help.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) Please also check the log file at "/var/lib/gdm3/.local/share/xorg/Xorg.0.log" for additional information.
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE)
Aug  4 18:07:47 COMP /usr/lib/gdm3/gdm-x-session[5106]: (EE) Server terminated with error (1). Closing log file
...

错误提交

• 见：https ://gitlab.freedesktop.org/mesa/mesa/-/issues/3372

建议的后续步骤

我怀疑启动问题是由最近的软件包更新引起的。我可能不小心安装了部分软件包Software Updater，因为我记得窗口中有一个警告。使系统恢复稳定状态的最佳方法是什么？

有关的

• 安装 PPA 后启动时屏幕变灰
• Mesa 3D 图形库

一步一步的解决方案

1. 由于“mesa”发生分段错误，我删除了上面列出的history.logsudo apt-get remove mesa-vdpau-drivers:amd64 mesa-va-drivers:amd64 libegl1-mesa-dev:amd64 mesa-common-dev:amd64 libglapi-mesa:amd64 libgl1-mesa-dri:amd64 libglx-mesa0:amd64中发生的所有包。结果 Ubuntu 开始进入 shell 提示符。
2. 然后我尝试安装一些最新的“mesa”包。我找到了ppa:kisak/kisak-mesa并通过sudo add-apt-repository ppa:kisak/kisak-mesa && sudo apt-get update.
3. 然后我在sudo apt-get install mesa-utils libglu1-mesa-dev xserver-xorg-video-all不知道需要什么的情况下通过安装。

仍然 UI 没有启动。

4. 然后我查看/var/log/dpkg.log并看到gdm3:amd64（GNOME 显示管理器）已被删除。我安装了它，重新启动，幸运的是可以再次登录。

但是桌面是空的，我无法启动任何文件夹。

5. 然后我重新安装nautilus并在注销并再次打开后重新出现桌面（图标和文件夹）。

基本上就是这样。

我在安装全新的 Ubuntu 20.04 时遇到了一个奇怪的问题。一切正常，除了原生 Linux 游戏。在 Rimworld 上，我在 Stardew Valley (Steam) 中得到了一张条纹图片，充其量所有文本框都显示亚洲语言。我已经尝试了很多东西，oibaf 驱动程序，奇怪的 grub 选项等等......但无济于事。 边缘世界截图

最奇怪的是，我所有使用 WINE 的 Windows 游戏都能完美运行。你有没有遇到过这样的事情？

TIA

此外，我尝试重新安装与 openGL 相关的所有内容，但仍然... Unigine Valley screenshot

我也试过改变记忆......同样的区别。我重新安装了 Windows 10，没有任何问题，因此排除了硬件故障。这真让人生气。

我刚刚从 AMD 的官方网站安装了 amdgpu-pro 驱动程序。但是现在有些应用程序运行得不是很好，我听说 Mesa 驱动程序更出色。

如何卸载这些驱动程序并用 Mesa 替换它们？

我从以下网址下载了驱动程序：https ://www.amd.com/en/support

遵循以下步骤：

1. tar -xJvf amdgpu-pro_*.tar.xz
2. cd amdgpu-pro-XX.XX-XXXXXX
3. ./amdgpu-pro-install -y

我有一个 Ryzen 3700x 和 RX 5700。似乎没有硬件加速，而且我似乎对所有东西都使用了软件渲染。我最近卸载了专有的 AMDGPU pro 驱动程序并从 18.04 升级到 Ubuntu 19.04，安装了 5.3-rc3 内核，并开始使用 oibaf 的 PPA。回到 Ubuntu 18.04 + AMDGPU pro 驱动程序是不必要的，因为对 Valve Index 的支持似乎不是那么好。除了等一会儿，我还能做些什么吗？

我在 ubuntu 19.04 代号为 disco dingo。

当我输入这个：

glxinfo | grep "OpenGL version"

我明白了

OpenGL version string: 4.6.0 NVIDIA 418.56

与二进制驱动程序相同：

$ glxinfo | grep "OpenGL version"
OpenGL version string: 4.4.0 NVIDIA 340.107

我希望我理解正确，但我认为 mesa 会随 ubuntu 19.04 一起提供吗？

我还做了以下事情：

sudo add-apt-repository ppa:ubuntu-x-swat/updates -y
sudo apt update
sudo apt full-upgrade -y

这没有帮助

我应该如何在 ubuntu 19.04 上获得台面？

使用了介子，缺少的依赖如下：

Found pkg-config: /usr/bin/pkg-config (0.29.1)
Dependency vdpau found: NO
Dependency xvmc found: NO
Dependency libomxil-bellagio found: NO
Dependency libtizonia found: NO
Dependency libtizplatform found: NO
Dependency tizilheaders found: NO
Dependency libva found: NO
meson.build:1088:0: ERROR: Native dependency 'zlib' not found

更新：

libegl1-mesa:
  Installed: 18.2.2-0ubuntu1~18.04.2
  Candidate: 18.2.2-0ubuntu1~18.04.2
  Version table:
 *** 18.2.2-0ubuntu1~18.04.2 500
        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     18.0.0~rc5-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
libgl1-mesa-dri:
  Installed: 18.2.2-0ubuntu1~18.04.2
  Candidate: 18.2.2-0ubuntu1~18.04.2
  Version table:
 *** 18.2.2-0ubuntu1~18.04.2 500
        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     18.0.0~rc5-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
libgl1-mesa-glx:
  Installed: 18.2.2-0ubuntu1~18.04.2
  Candidate: 18.2.2-0ubuntu1~18.04.2
  Version table:
 *** 18.2.2-0ubuntu1~18.04.2 500
        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     18.0.0~rc5-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
N: Unable to locate package libglx-mesa

我的笔记本电脑具有 ubuntu 18.10 以及 Intel HD620 和 Nvidia 940mx 的混合显卡。当我切换 Nvidia 图形时，它可以零延迟工作，但 Intel 图形滞后，所以我为 Intel 安装了 mesa 18.1.1。我怀疑ubuntu是否会与两个驱动程序冲突。因为我有一次禁用 IRQ #16 错误。所以我想知道安装这两个驱动程序是否可以，并且英特尔将使用 Mesa 和 Nvidia 仅使用 415.25 吗？当我使用 sudo prime-select 时，驱动程序会正确切换吗？

我将附加到最终以这种情况结束的教程。 https://github.com/lutris/lutris/wiki/How-to:-DXVK