AskOverflow.Dev

AskOverflow.Dev Logo AskOverflow.Dev Logo

AskOverflow.Dev Navigation

    • 主页
    • 系统&网络
    • Ubuntu
    • Unix
    • DBA
    • Computer
    • Coding
    • LangChain

Mobile menu

Close
  • 主页
  • 系统&网络
    • 最新
    • 热门
    • 标签
  • Ubuntu
    • 最新
    • 热门
    • 标签
  • Unix
    • 最新
    • 标签
  • DBA
    • 最新
    • 标签
  • Computer
    • 最新
    • 标签
  • Coding
    • 最新
    • 标签
主页 / ubuntu / 问题

问题[lightdm](ubuntu)

Martin Hope
mikemtnbikes
Asked: 2024-06-15 05:53:03 +0800 CST

显示管理器 lightdm 停止工作

  • 6

最近我的 lightdm 停止正常工作(请注意,只有启动到恢复模式或在我的 linux 启动参数中添加“nomodeset”时,我才能获得欢迎屏幕。但是,使用 nomodeset 似乎会阻止我在暂停会话后恢复会话。)

这个问题似乎是在我使用外接显示器后开始的,然后 lightdm 想要使用它,但我删除了我的~/.config/monitors.xml,使用sudo dpkg-reconfigure xserver-xorg并且在使用“nomodeset”启动时没有看到有关丢失显示器的消息,所以我不确定这是否仍然是一个问题。

有人能帮我找出与我的显示器相关的哪些设置缺失/搞砸了吗?

以下是基本信息

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.4 LTS
Release:        22.04
Codename:       jammy


$  sudo lshw -c display
  *-display
       description: VGA compatible controller
       product: Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:04:00.0
       version: c1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
       configuration: driver=amdgpu latency=0
       resources: irq:24 memory:e0000000-efffffff memory:f0000000-f01fffff ioport:e000(size=256) memory:fe800000-fe87ffff


$ sudo systemctl status lightdm
× lightdm.service - Light Display Manager
     Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2024-06-14 17:09:40 EDT; 14s ago
       Docs: man:lightdm(1)
    Process: 4436 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS)
    Process: 4439 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
   Main PID: 4439 (code=exited, status=1/FAILURE)
        CPU: 108ms

Jun 14 17:09:40 computer systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Jun 14 17:09:40 computer systemd[1]: Stopped Light Display Manager.
Jun 14 17:09:40 computer systemd[1]: lightdm.service: Start request repeated too quickly.
Jun 14 17:09:40 computer systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jun 14 17:09:40 computer systemd[1]: Failed to start Light Display Manager.

以下是 /var/log/lightdm/ 的输出

[+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=4439
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-arctica-greeter-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-arctica-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /var/lib/flatpak/exports/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/90-arctica-greeter.conf
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/91-arctica-greeter-guest-session.conf
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/91-arctica-greeter-mate.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:*], please update this configuration
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 4444: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.27s] DEBUG: Process 2086 terminated with signal 6
[+0.27s] DEBUG: XServer 0: X server stopped
[+0.27s] DEBUG: Releasing VT 7
[+0.27s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.27s] DEBUG: Seat seat0: Display server stopped
[+0.27s] DEBUG: Seat seat0: Stopping session
[+0.27s] DEBUG: Seat seat0: Session stopped
[+0.27s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.27s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.27s] DEBUG: Seat seat0: Stopping
[+0.27s] DEBUG: Seat seat0: Stopped
[+0.27s] DEBUG: Required seat has stopped
[+0.27s] DEBUG: Stopping display manager
[+0.27s] DEBUG: Display manager stopped
[+0.27s] DEBUG: Stopping daemon
[+0.27s] DEBUG: Exiting with return value 1

还有更多

$ sudo less x-0.log
X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
Current Operating System: Linux computer 5.15.0-112-generic #122-Ubuntu SMP Thu May 23 07:48:21 UTC 2024 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-112-generic root=UUID=742c43fb-bb10-4440-9d51-747c120972f6 ro resume=UUID=e03ba40a-11c4-4e82-84a5-25624f8926a7
xorg-server 2:21.1.4-2ubuntu1.7~22.04.10 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.40.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 14 17:29:04 2024
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
vesa: Ignoring device with a bound kernel driver
vesa: Ignoring device with a bound kernel driver
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.

/var/log/Xorg.0.log 的输出很长,完整的输出发布在这里,但简而言之,

$ grep -A2 -B2  "\((EE)\|(WW)\)" /var/log/Xorg.0.log
[    40.356] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    40.356] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 14 17:29:04 2024
[    40.356] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
--
[    40.357] (==) Automatically binding GPU devices
[    40.357] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    40.358] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    40.358]    Entry deleted from font path.
[    40.358] (==) FontPath set to:
--
[    40.447] (II) FBDEV: driver for framebuffer: fbdev
[    40.447] (II) VESA: driver for VESA chipsets: vesa
[    40.447] (EE) open /dev/dri/card0: No such file or directory
[    40.447] (WW) Falling back to old probe method for modesetting
[    40.447] (EE) open /dev/dri/card0: No such file or directory
[    40.447] (II) Loading sub module "fbdevhw"
[    40.447] (II) LoadModule: "fbdevhw"
--
[    40.447]    compiled for 1.21.1.4, module version = 0.0.2
[    40.447]    ABI class: X.Org Video Driver, version 25.2
[    40.447] (EE) Unable to find a valid framebuffer device
[    40.447] (WW) Falling back to old probe method for fbdev
[    40.447] (II) Loading sub module "fbdevhw"
[    40.447] (II) LoadModule: "fbdevhw"
--
[    40.447]    compiled for 1.21.1.4, module version = 0.0.2
[    40.448]    ABI class: X.Org Video Driver, version 25.2
[    40.448] (EE) open /dev/fb0: No such file or directory
[    40.448] vesa: Ignoring device with a bound kernel driver
[    40.448] (EE) Screen 0 deleted because of no matching config section.
[    40.448] (II) UnloadModule: "modesetting"
[    40.448] (EE) Screen 0 deleted because of no matching config section.
[    40.448] (II) UnloadModule: "fbdev"
[    40.448] (II) UnloadSubModule: "fbdevhw"
[    40.448] (EE) Screen 0 deleted because of no matching config section.
[    40.448] (II) UnloadModule: "vesa"
[    40.448] (EE) Device(s) detected, but none match those in the config file.
[    40.448] (==) Matched ati as autoconfigured driver 0
[    40.448] (==) Matched modesetting as autoconfigured driver 1
--
[    40.453] (II) FBDEV: driver for framebuffer: fbdev
[    40.453] (II) VESA: driver for VESA chipsets: vesa
[    40.453] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[    40.453] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[    40.453] (EE) open /dev/dri/card0: No such file or directory
[    40.453] (WW) Falling back to old probe method for modesetting
[    40.453] (EE) open /dev/dri/card0: No such file or directory
[    40.453] (II) Loading sub module "fbdevhw"
[    40.453] (II) LoadModule: "fbdevhw"
--
[    40.453]    compiled for 1.21.1.4, module version = 0.0.2
[    40.453]    ABI class: X.Org Video Driver, version 25.2
[    40.453] (EE) Unable to find a valid framebuffer device
[    40.453] (WW) Falling back to old probe method for fbdev
[    40.453] (II) Loading sub module "fbdevhw"
[    40.453] (II) LoadModule: "fbdevhw"
--
[    40.453]    compiled for 1.21.1.4, module version = 0.0.2
[    40.453]    ABI class: X.Org Video Driver, version 25.2
[    40.453] (EE) open /dev/fb0: No such file or directory
[    40.453] vesa: Ignoring device with a bound kernel driver
[    40.453] (EE) Screen 0 deleted because of no matching config section.
[    40.453] (II) UnloadModule: "modesetting"
[    40.453] (EE) Screen 0 deleted because of no matching config section.
[    40.453] (II) UnloadModule: "fbdev"
[    40.453] (II) UnloadSubModule: "fbdevhw"
[    40.453] (II) UnloadSubModule: "fbdevhw"
[    40.453] (II) UnloadSubModule: "fbdevhw"
[    40.453] (EE) Screen 0 deleted because of no matching config section.
[    40.453] (II) UnloadModule: "vesa"
[    40.453] (EE) Device(s) detected, but none match those in the config file.
[    40.453] (EE)
Fatal server error:
[    40.453] (EE) no screens found(EE)
[    40.454] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    40.454] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    40.454] (EE)
[    40.454] (EE) Server terminated with error (1). Closing log file.

我试过使用 gdm3,但它也不起作用,例如

sudo systemctl status gdm3
● gdm.service - GNOME Display Manager
     Loaded: loaded (/lib/systemd/system/gdm.service; static)
     Active: active (running) since Fri 2024-06-14 17:47:20 EDT; 26s ago
    Process: 28929 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
   Main PID: 28934 (gdm3)
      Tasks: 3 (limit: 11688)
     Memory: 2.8M
        CPU: 301ms
     CGroup: /system.slice/gdm.service
             └─28934 /usr/sbin/gdm3

Jun 14 17:47:31 computer gdm3[28934]: Gdm: GdmDisplay: Session never registered, failing
Jun 14 17:47:31 computer gdm3[28934]: Gdm: Child process -29017 was already dead.
Jun 14 17:47:31 computer gdm-launch-environment][29021]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=130) by LOGIN(uid=0)
Jun 14 17:47:31 computer gdm-launch-environment][29021]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Jun 14 17:47:31 computer gdm3[28934]: Gdm: GdmDisplay: Session never registered, failing
Jun 14 17:47:31 computer gdm-launch-environment][29021]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 14 17:47:31 computer gdm3[28934]: Gdm: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Jun 14 17:47:31 computer gdm3[28934]: Gdm: Child process -29027 was already dead.
Jun 14 17:47:31 computer gdm3[28934]: Gdm: GdmDisplay: Session never registered, failing
Jun 14 17:47:31 computer gdm3[28934]: Gdm: Child process -29027 was already dead.
lightdm
  • 2 个回答
  • 90 Views
Martin Hope
bog
Asked: 2024-02-09 10:07:17 +0800 CST

raspi5 23.10 无法从 gdm3 切换到 lightdm

  • 6

我已经在 Raspberry Pi 5 上安装了 23.10,一切看起来都很不错。

默认的显示管理器是gdm3,符合23.10当前的祝福GUI,左侧有栏等等。(我不知道那个 UI 叫什么;我不喜欢它。)

因此,我试图切换到过去多年来我在所有其他系统上使用的常用 xubuntu 东西。

一切似乎都很好。我可以通过 Synaptic 进行工作并安装所有常用组件。只要我不切换到 lightdm,我就需要获得我喜欢的 UI。

如果,当不需要的用户界面一切正常时,我会创建一个终端窗口并输入

sudo dpkg-重新配置 lightdm

它提供了预期的选择。如果我选择 lightdm 并重新启动,我会看到一个完整(我认为;可能是 VGA)分辨率图形模式对话框,其中显示

!系统正在低图形模式下运行无法正确检测您的屏幕、图形卡和输入设备设置。您需要自己配置这些。

如果我点击“确定”,它会出现一系列对话框,提供诸如“重新配置图形”、“排除错误”等内容,但这些对话框都不会产生任何实际有用的东西。

如果我使用 Ctrl-Alt F3(例如)切换到另一个控制台,我可以切换回 gdm3,并且在重新启动后,一切都会回到不需要的 UI。

查看/var/log/Xorg.0.log,它以

[147.052] ABI 类:X.Org 视频驱动程序,版本 25.2 [147.052] (II) FBDEV(0):使用默认设备 [147.064] (II) 模式集 (G0):使用 drv /dev/dri/card1 [147.065] (WW) VGA 仲裁器:无法打开内核仲裁器,无多卡支持 [ 147.065] (EE) 致命服务器错误: [ 147.0!系统正在低图形模式下运行无法正确检测您的屏幕、图形卡和输入设备设置。您需要自己配置这些。65] (EE) 无法在帧缓冲模式下运行。请指定所有帧缓冲区设备的总线ID [ 147.065] (EE) [ 147.065] (EE) 请访问http://wiki.x.org咨询 X.Org 基金会支持以 获取帮助。[ 147.065] (EE) 另请检查“/var/log/Xorg.0.log”处的日志文件以获取更多信息。[
147.065] (EE) [ 147.116] (EE) 服务器因错误 (1) 终止。关闭日志文件。

看来,到 23.10 为止,rpi5 的图形功能还不足以运行 lightdm。

距离我尝试解决 X Window 系统启动问题还不到 30 年,所以这对我来说是个深奥的问题。

有人有什么建议吗?

lightdm
  • 1 个回答
  • 33 Views
Martin Hope
Lysanderoth
Asked: 2021-04-25 07:42:55 +0800 CST

夜灯在 LightDm 上不起作用

  • 1

我正在运行 Ubuntu 20.04.2,最近将我的桌面管理器从 gdm3 切换到 lightdm,因为 gdm3 的 GUI 在出现一些 NVIDIA 驱动程序问题后无法正常工作。到目前为止,lightdm 的运行情况要好得多。但是,我确实有一个问题:设置 > 显示 > 夜灯中的夜灯选项不再起作用。我可以打开它并设置手动时间,但它在我的桌面上没有明显的效果。在桌面的右上角,有wifi设置和电源按钮,它甚至说夜灯是开着的。但是桌面看起来没有什么不同,更改“色温”滑块也没有什么不同。如何解决此问题以使夜灯正常工作?

lightdm
  • 1 个回答
  • 270 Views
Martin Hope
Danyal Mughal
Asked: 2020-12-12 21:21:28 +0800 CST

在 Ubuntu 18.04.4 上出现显示问题

  • 0

在运行 docker 进行刮擦/飞溅时,我不断收到“Empty Trash”的通知,这表明磁盘空间不足。

几秒钟后,GUI 卡住了。我通过电源按钮为笔记本电脑供电。

然后在启动时,我收到这样的消息

Started GNOME display manager... and deal with any system changes..p link was shut down.....

所以我尝试了这个结果

问 ubuntu 答案

如图所示,我也尝试使用此答案进行清理,但没有得到任何结果。

更新

我的硬盘看起来像这样

硬盘状况

gdm disk-usage display-manager lightdm 18.04
  • 1 个回答
  • 56 Views
Martin Hope
Zany_Zachary1
Asked: 2020-11-05 09:54:30 +0800 CST

LightDM 主题不正常

  • 2

各位 Ubuntu 爱好者!我最近通过安装 LightDM sudo apt install lightdm,然后通过安装 lightdm 设置工具sudo apt-get install lightdm-gtk-greeter-settings
现在,LightDM 看起来很奇怪。它没有以前安装全新 lightDM 时的外观。有人可以帮我恢复所有设置吗?
我的 lightDM 主题现在看起来像这样:
在此处输入图像描述 但我希望它看起来像这样:
在此处输入图像描述 顺便说一下,我在 Ubuntu 20.04 上,Focal Fossa。

themes unity login display-manager lightdm
  • 1 个回答
  • 332 Views
Martin Hope
Paradox174
Asked: 2020-10-30 07:46:01 +0800 CST

如何在 Ubuntu MATE 中删除额外的访客帐户?/ 如何让我的访客帐户正常工作?

  • 0

我在 Ubuntu MATE 中遇到来宾会话问题;每次我尝试登录时,它都会告诉我无法访问 .ICEauthority 文件(不记得它的位置),将我引导出去,并创建一个名为 Guest 的新帐户。因此,我不仅无法进入我的访客帐户,而且每当我尝试时,它都会创建一个名为 Guest 的新帐户。我无法登录它们(密码被锁定,我不知道它是什么)并且它们不会出现在用户和组中。有谁知道如何解决这些问题?

guest-session lightdm mate
  • 1 个回答
  • 435 Views
Martin Hope
Athena Wisdom
Asked: 2020-09-09 07:54:55 +0800 CST

在 Ubuntu 20.04 上恢复原始登录屏幕

  • 1

在全新的 Ubuntu 20.04 安装中,我安装了 Unity 并将其配置为lightdm在安装向导中使用。登录屏幕看起来不同了,我们现在可以在登录前选择要使用的桌面环境。

sudo apt install ubuntu-unity-desktop

在此处输入图像描述

然后我决定通过卸载 Unity 切换回默认的 GNOME 桌面。但是,即使在重新启动计算机后,登录屏幕也不会回到新安装的 Ubuntu 20.04 随附的原始屏幕。

sudo apt purge unity-session unity
sudo apt autoremove
sudo apt install ubuntu-session gdm3

我们如何在 Ubuntu 20.04 中恢复原始登录屏幕?

gnome login lightdm unity-greeter 20.04
  • 1 个回答
  • 3364 Views
Martin Hope
Deva
Asked: 2020-08-23 12:46:31 +0800 CST

已卸载 Lightdm

  • 2

在此处输入图像描述我错误地从我的电脑上卸载了 lightdm,然后重新启动了我的电脑,我什至无法登录以安装它(它在登录页面中循环,并且在终端中也发生了同样的事情)我使用单用户模式 ​​hack 进入了 shell,但是那里我的wifi接口不工作我无法连接到我的wifi来安装lightdm编辑:我认为我的bash坏了,因为没有安装它们都返回错误:处理bash时遇到的错误

software-installation lightdm 20.04
  • 2 个回答
  • 1001 Views
Martin Hope
Michael Paccione
Asked: 2020-07-21 21:46:54 +0800 CST

Xinerama 1 卡在登录 [lightdm]

  • 2

我正在尝试使用 GeForce 970GTX + Steam Proton 的 Xinerama 1。现在,我用 GDM3 尝试了这个,Xinerama 1 会导致黑屏。我正在运行 390 驱动程序。

为了让它工作,我切换到 lightdm。实际上,Xinerama 会显示屏幕,但登录后会卡住。所以我登录了……它显示了一个放大的动物背景,分布在三个屏幕上。但是,它无法完成我正常桌面的登录过程。所以它没有图标或菜单,只能访问 TTY 而不是 ctrl + t 终端。

我觉得我很接近。自从我放入新卡以来,我已经花了大约 4 个小时进行调试。有任何想法吗?

nvidia xinerama lightdm
  • 1 个回答
  • 503 Views
Martin Hope
Osama Arshad Dar
Asked: 2020-07-17 12:06:57 +0800 CST

Ubuntu 18.04 卡在启动分段错误 XServer

  • 2

我有一台运行 Ubuntu 18.04 LTS 的联想 E570 机器(带有 Nvidia GTX 950M)。直到今天早上 Ubuntu 启动卡在Started Gnome Display Manager. 有趣的是,如果我进入恢复模式然后恢复正常启动,我的桌面环境是可以访问的。

脚步

遇到此错误后,我尝试了几件事:

  1. 根据这个答案,我删除了 Nvidia 驱动程序。
  2. 删除 gdm3(Gnome 桌面管理器)并重新安装
  3. 安装并尝试了不同的桌面管理器,包括 LightDM、SliM(并将它们一一设为主要桌面管理器),但这也不起作用(附加日志)。
  4. 从第 3 步的日志中发现这是 X.Org X Server 的问题(附有日志)。删除并再次安装包xserver-xorg
  5. 从 Ubuntu 软件更新管理器安装 Nvidia 驱动程序

以上选项似乎都不适合我。我在这里想念什么?

我的 Linux 内核是 4.15.0-109-generic

日志

  1. /var/log/lightdm/lightdm.log
[+24.84s] DEBUG: Session pid=1658: Running command /usr/sbin/lightdm-session env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
[+24.84s] DEBUG: Creating shared data directory /var/lib/lightdm-data/osama
[+24.84s] DEBUG: Session pid=1658: Logging to .xsession-errors
[+24.92s] DEBUG: Activating VT 7
[+24.92s] DEBUG: Activating login1 session c2
[+24.92s] DEBUG: Seat seat0 changes active session to c2
[+24.92s] DEBUG: Session c2 is already active
[+272.84s] DEBUG: Got signal 15 from process 1
[+272.84s] DEBUG: Caught Terminated signal, shutting down
[+272.84s] DEBUG: Stopping display manager
[+272.84s] DEBUG: Seat seat0: Stopping
[+272.84s] DEBUG: Seat seat0: Stopping display server
[+272.84s] DEBUG: Sending signal 15 to process 1232
[+272.84s] DEBUG: Seat seat0: Stopping session
[+272.84s] DEBUG: Terminating login1 session c2
[+272.85s] DEBUG: Session pid=1658: Sending SIGTERM
[+272.93s] DEBUG: Session pid=1658: Exited with return value 0
[+272.93s] DEBUG: Seat seat0: Session stopped
[+272.93s] DEBUG: Seat seat0 changes active session to 
[+273.17s] DEBUG: Process 1232 exited with return value 0
[+273.17s] DEBUG: XServer 0: X server stopped
[+273.17s] DEBUG: Releasing VT 7
[+273.17s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+273.17s] DEBUG: Seat seat0: Display server stopped
[+273.17s] DEBUG: Seat seat0: Stopped
[+273.17s] DEBUG: Display manager stopped
[+273.17s] DEBUG: Stopping daemon
[+273.17s] DEBUG: Exiting with return value 0
  1. /var/log/slim.log
slim: waiting for X server to begin accepting connections Giving up. slim: unable to connect to X server


slim: waiting for X server to begin accepting connections Giving up. slim: unable to connect to X server
  1. /var/log/Xorg.0.log.old
[    13.050] (II) Module glx: vendor="X.Org Foundation"
[    13.050]  compiled for 1.19.6, module version = 1.0.0
[    13.050]  ABI class: X.Org Server Extension, version 10.0
[    13.050] (==) Matched modesetting as autoconfigured driver 0
[    13.050] (==) Matched fbdev as autoconfigured driver 1
[    13.050] (==) Matched vesa as autoconfigured driver 2
[    13.050] (==) Assigned the driver to the xf86ConfigLayout
[    13.050] (II) LoadModule: "modesetting"
[    13.050] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    13.050] (II) Module modesetting: vendor="X.Org Foundation"
[    13.050]  compiled for 1.19.6, module version = 1.19.6
[    13.050]  Module class: X.Org Video Driver
[    13.050]  ABI class: X.Org Video Driver, version 23.0
[    13.050] (II) LoadModule: "fbdev"
[    13.050] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    13.050] (II) Module fbdev: vendor="X.Org Foundation"
[    13.050]  compiled for 1.19.3, module version = 0.4.4
[    13.050]  Module class: X.Org Video Driver
[    13.050]  ABI class: X.Org Video Driver, version 23.0
[    13.050] (II) LoadModule: "vesa"
[    13.051] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    13.051] (II) Module vesa: vendor="X.Org Foundation"
[    13.051]  compiled for 1.19.3, module version = 2.3.4
[    13.051]  Module class: X.Org Video Driver
[    13.051]  ABI class: X.Org Video Driver, version 23.0
[    13.051] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    13.051] (II) FBDEV: driver for framebuffer: fbdev
[    13.051] (II) VESA: driver for VESA chipsets: vesa
[    13.079] (II) modeset(0): using drv /dev/dri/card0
[    13.079] (WW) Falling back to old probe method for fbdev
[    13.079] (II) Loading sub module "fbdevhw"
[    13.079] (II) LoadModule: "fbdevhw"
[    13.080] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    13.080] (II) Module fbdevhw: vendor="X.Org Foundation"
[    13.080]  compiled for 1.19.6, module version = 0.0.2
[    13.080]  ABI class: X.Org Video Driver, version 23.0
[    13.080] (WW) Falling back to old probe method for vesa
[    13.080] (II) modeset(0): Creating default Display subsection in Screen section
  "Default Screen Section" for depth/fbbpp 24/32
[    13.080] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    13.080] (==) modeset(0): RGB weight 888
[    13.080] (==) modeset(0): Default visual is TrueColor
[    13.080] (II) Loading sub module "glamoregl"
[    13.080] (II) LoadModule: "glamoregl"
[    13.080] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    13.083] (II) Module glamoregl: vendor="X.Org Foundation"
[    13.083]  compiled for 1.19.6, module version = 1.0.0
[    13.083]  ABI class: X.Org ANSI C Emulation, version 0.4
[    13.083] (II) glamor: OpenGL accelerated X.org driver based.
[    13.101] (EE) 
[    13.101] (EE) Backtrace:
[    13.101] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x55f3d6f7f8cd]
[    13.101] (EE) 1: /usr/lib/xorg/Xorg (0x55f3d6dc7000+0x1bc669) [0x55f3d6f83669]
[    13.101] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f8341fac000+0x128a0) [0x7f8341fbe8a0]
>     [    13.101] (EE) 3: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7f83393f3000+0x129cc) [0x7f83394059cc]
>     [    13.101] (EE) 4: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7f83393f3000+0x1b19e) [0x7f833940e19e]
>     [    13.101] (EE) 5: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7f83393f3000+0x216df) [0x7f83394146df]
>     [    13.102] (EE) 6: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7f83393f3000+0x1ac0b) [0x7f833940dc0b]
>     [    13.102] (EE) 7: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7f83393f3000+0x16b7d) [0x7f8339409b7d]
>     [    13.102] (EE) 8: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7f83393f3000+0x16bc5) [0x7f8339409bc5]
>     [    13.102] (EE) 9: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 (0x7f83393f3000+0x10948) [0x7f8339403948]
>     [    13.102] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x10b) [0x7f833e845c9b]
>     [    13.102] (EE) 11: /usr/lib/xorg/modules/drivers/modesetting_drv.so (0x7f833f083000+0x9dc9) [0x7f833f08cdc9]
>     [    13.102] (EE) 12: /usr/lib/xorg/Xorg (InitOutput+0xc08) [0x55f3d6e60288]
>     [    13.102] (EE) 13: /usr/lib/xorg/Xorg (0x55f3d6dc7000+0x56cd3) [0x55f3d6e1dcd3]
>     [    13.102] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7f8341bdcb97]
>     [    13.102] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2a) [0x55f3d6e07b8a]
>     [    13.102] (EE) 
>     [    13.102] (EE) Segmentation fault at address 0x55f3d90000f7
>     [    13.102] (EE) 
>     Fatal server error:
>     [    13.102] (EE) Caught signal 11 (Segmentation fault). Server aborting
>     [    13.102] (EE) 
>     [    13.102] (EE) 
>     Please consult the The X.Org Foundation support 
>        at http://wiki.x.org
>      for help. 
>     [    13.102] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
>     [    13.102] (EE) 
>     [    13.133] (EE) Server terminated with error (1). Closing log file.
xorg drivers nvidia lightdm 18.04
  • 1 个回答
  • 2107 Views

Sidebar

Stats

  • 问题 205573
  • 回答 270741
  • 最佳答案 135370
  • 用户 68524
  • 热门
  • 回答
  • Marko Smith

    如何运行 .sh 脚本?

    • 16 个回答
  • Marko Smith

    如何安装 .tar.gz(或 .tar.bz2)文件?

    • 14 个回答
  • Marko Smith

    如何列出所有已安装的软件包

    • 24 个回答
  • Marko Smith

    无法锁定管理目录 (/var/lib/dpkg/) 是另一个进程在使用它吗?

    • 25 个回答
  • Martin Hope
    Flimm 如何在没有 sudo 的情况下使用 docker? 2014-06-07 00:17:43 +0800 CST
  • Martin Hope
    Ivan 如何列出所有已安装的软件包 2010-12-17 18:08:49 +0800 CST
  • Martin Hope
    La Ode Adam Saputra 无法锁定管理目录 (/var/lib/dpkg/) 是另一个进程在使用它吗? 2010-11-30 18:12:48 +0800 CST
  • Martin Hope
    David Barry 如何从命令行确定目录(文件夹)的总大小? 2010-08-06 10:20:23 +0800 CST
  • Martin Hope
    jfoucher “以下软件包已被保留:”为什么以及如何解决? 2010-08-01 13:59:22 +0800 CST
  • Martin Hope
    David Ashford 如何删除 PPA? 2010-07-30 01:09:42 +0800 CST

热门标签

10.10 10.04 gnome networking server command-line package-management software-recommendation sound xorg

Explore

  • 主页
  • 问题
    • 最新
    • 热门
  • 标签
  • 帮助
subwaysurfers
my femboy roommate

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve