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
    • 最新
    • 标签
主页 / user-241361

mikemtnbikes's questions

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
mikemtnbikes
Asked: 2023-07-10 22:16:22 +0800 CST

ESM 补丁最终会与社区共享吗?

  • 9

我想我了解 ESM 服务的基本机制,但不清楚 Canonical 提供的补丁是什么。我可以想象发布 ESM 模型下的 2 个场景,并想知道是哪一个(如果有的话)。是吗,

  1. Canonical 将创建修复程序,但仅与“Ubuntu Pro”用户共享,而不与更广泛的社区共享。(这大概是各种许可证允许的)?
  2. 或者,Canonical 是否会将主流代码构建到.deb包中并提供这些代码?
  3. 还有别的事吗?

如果是 1.,Canonical 的安全补丁最终会与原始软件开发人员或更广泛的社区共享吗?

updates
  • 1 个回答
  • 448 Views
Martin Hope
mikemtnbikes
Asked: 2022-01-07 13:06:32 +0800 CST

为什么 Ubuntu 不提供 emacs .el 文件的编译版本

  • 0

我刚刚注意到,当我在 MATE 20.04 上启动 emacs 时,它加载的系统包是源文件,而不是它们的二进制文件。我很想知道为什么,因为据我所知,二进制文件的加载速度要快得多。

例如,

Loading /etc/emacs/site-start.d/00debian.el (source)...done
Loading /etc/emacs/site-start.d/50auctex.el (source)...
Loading /usr/share/emacs/site-lisp/auctex.el (source)...done
Loading /usr/share/emacs/site-lisp/preview-latex.el (source)...done
Loading /etc/emacs/site-start.d/50auctex.el (source)...done
.
.
.
Loading personal...
Loading no-x-settings...done
Loading ssh...done
emacs
  • 1 个回答
  • 43 Views
Martin Hope
mikemtnbikes
Asked: 2021-12-27 15:47:58 +0800 CST

lightdm 尝试使用不存在的外部显示器

  • 0

我在登录我的 X 会话和/或从暂停状态恢复时遇到问题。

从大约 6 个月前开始,我的桌面管理器 lightdm 开始出现问题(尽管我尝试过其他类似 gdm3 的管理器并得到相同的行为)。

在我使用外接显示器后,问题就会开始出现。似乎不是在我的笔记本电脑上显示欢迎屏幕,而是尝试使用不存在的外部显示器。在笔记本电脑显示屏上,我看到一个几乎空白的屏幕,左上角有一个下划线“_”。

这种行为特别烦人,因为它试图使用外接显示器,我什至无法访问任何虚拟终端,必须硬重启进入恢复模式。值得注意的是,如果我使用恢复模式启动然后选择resume,我会收到欢迎程序并可以登录。

/etc/lightdm/lightdm.conf最终,当我使用以下内容创建文件时,我似乎解决了问题

[Seat:*]
display-setup-script=xrandr --output eDP --primary

这似乎解决了问题,即我可以使用正常的启动过程,在我的笔记本电脑显示器上获取欢迎程序,并在需要时使用外部显示器。

但是,从上周开始,此修复程序不再有效。我已经重新启动,运行apt upgrade和apt update. 删除并重新安装了各种 lightdm .deb 文件,使用过dpkg-reconfigure,重新安装了 gdm3,...

我当前的内核是5.4.0-91-generic #102-Ubuntu并且我正在运行 MATE 20.04 LTS。这是一台运行 Ryzen-7 处理器和 Radeon 显卡的惠普笔记本电脑。

之前运行的 lshw 给出了

   *-display
        description: VGA compatible controller
        product: Picasso
        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:50 memory:e0000000-efffffff memory:f0000000-f01fffff ioport:e000(size=256) memory:fe800000-fe87ffff

当前设置(恢复 -> 恢复)

$ sudo lshw -c video |less
*-display UNCLAIMED
   description: VGA compatible controller
   product: Picasso
   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: latency=0
   resources: memory:e0000000-efffffff memory:f0000000-f01fffff ioport:e000(size=256) memory:fe800000-fe87ffff

注意行的变化configuration:。

$ apt search amdgpu表示我已安装 amdgpu。

以下是 /var/log/Xorg.0.log 中的输出

[    10.370] 
X.Org X Server 1.20.13
X Protocol Version 11, Revision 0
[    10.370] Build Operating System: linux Ubuntu
[    10.370] Current Operating System: Linux alanine 5.4.0-91-generic #102-Ubuntu SMP Fri Nov 5 16:31:28 UTC 2021 x86_64
[    10.370] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=742c43fb-bb10-4440-9d51-747c120972f6 ro
[    10.371] Build Date: 14 December 2021  02:14:13PM
[    10.371] xorg-server 2:1.20.13-1ubuntu1~20.04.2 (For technical support please see http://www.ubuntu.com/support) 
[    10.371] Current version of pixman: 0.38.4
[    10.371]    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[    10.371] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    10.371] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 26 17:08:36 2021
[    10.373] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    10.374] (==) No Layout section.  Using the first Screen section.
[    10.374] (==) No screen section available. Using defaults.
[    10.374] (**) |-->Screen "Default Screen Section" (0)
[    10.374] (**) |   |-->Monitor "<default monitor>"
[    10.374] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
[    10.375] (==) Automatically adding devices
[    10.375] (==) Automatically enabling devices
[    10.375] (==) Automatically adding GPU devices
[    10.375] (==) Automatically binding GPU devices
[    10.375] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    10.376] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    10.376]    Entry deleted from font path.
[    10.377] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/100dpi/".
[    10.377]    Entry deleted from font path.
[    10.377]    (Run 'mkfontdir' on "/usr/share/fonts/X11/100dpi/").
[    10.378] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/75dpi/".
[    10.378]    Entry deleted from font path.
[    10.378]    (Run 'mkfontdir' on "/usr/share/fonts/X11/75dpi/").
[    10.378] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/100dpi".
[    10.378]    Entry deleted from font path.
[    10.378]    (Run 'mkfontdir' on "/usr/share/fonts/X11/100dpi").
[    10.378] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/75dpi".
[    10.378]    Entry deleted from font path.
[    10.378]    (Run 'mkfontdir' on "/usr/share/fonts/X11/75dpi").
[    10.378] (==) FontPath set to:
    /usr/share/fonts/X11/misc,
    /usr/share/fonts/X11/Type1,
    built-ins
[    10.378] (==) ModulePath set to "/usr/lib/xorg/modules"
[    10.378] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
[    10.378] (II) Loader magic: 0x556edcc6e020
[    10.378] (II) Module ABI versions:
[    10.378]    X.Org ANSI C Emulation: 0.4
[    10.378]    X.Org Video Driver: 24.1
[    10.378]    X.Org XInput driver : 24.1
[    10.378]    X.Org Server Extension : 10.0
[    10.379] (++) using VT number 7

[    10.379] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    10.380] (II) xfree86: Adding drm device (/dev/dri/card0)
[    10.393] (--) PCI:*(4@0:0:0) 1002:15d8:103c:86fd rev 193, Mem @ 0xe0000000/268435456, 0xf0000000/2097152, 0xfe800000/524288, I/O @ 0x0000e000/256
[    10.393] (II) LoadModule: "glx"
[    10.395] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    10.403] (II) Module glx: vendor="X.Org Foundation"
[    10.403]    compiled for 1.20.13, module version = 1.0.0
[    10.403]    ABI class: X.Org Server Extension, version 10.0
[    10.403] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0
[    10.403]    loading driver: amdgpu
[    10.403] (==) Matched amdgpu as autoconfigured driver 0
[    10.403] (==) Matched ati as autoconfigured driver 1
[    10.403] (==) Matched modesetting as autoconfigured driver 2
[    10.403] (==) Matched fbdev as autoconfigured driver 3
[    10.403] (==) Matched vesa as autoconfigured driver 4
[    10.403] (==) Assigned the driver to the xf86ConfigLayout
[    10.403] (II) LoadModule: "amdgpu"
[    10.403] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[    10.409] (II) Module amdgpu: vendor="X.Org Foundation"
[    10.409]    compiled for 1.20.5, module version = 19.1.0
[    10.409]    Module class: X.Org Video Driver
[    10.409]    ABI class: X.Org Video Driver, version 24.0
[    10.409] (II) LoadModule: "ati"
[    10.409] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[    10.410] (II) Module ati: vendor="X.Org Foundation"
[    10.410]    compiled for 1.20.5, module version = 19.1.0
[    10.410]    Module class: X.Org Video Driver
[    10.410]    ABI class: X.Org Video Driver, version 24.0
[    10.423] (II) LoadModule: "modesetting"
[    10.423] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    10.424] (II) Module modesetting: vendor="X.Org Foundation"
[    10.424]    compiled for 1.20.13, module version = 1.20.13
[    10.424]    Module class: X.Org Video Driver
[    10.424]    ABI class: X.Org Video Driver, version 24.1
[    10.424] (II) LoadModule: "fbdev"
[    10.424] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    10.425] (II) Module fbdev: vendor="X.Org Foundation"
[    10.425]    compiled for 1.20.1, module version = 0.5.0
[    10.425]    Module class: X.Org Video Driver
[    10.425]    ABI class: X.Org Video Driver, version 24.0
[    10.425] (II) LoadModule: "vesa"
[    10.425] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    10.425] (II) Module vesa: vendor="X.Org Foundation"
[    10.425]    compiled for 1.20.4, module version = 2.4.0
[    10.425]    Module class: X.Org Video Driver
[    10.425]    ABI class: X.Org Video Driver, version 24.0
[    10.425] (II) AMDGPU: Driver for AMD Radeon:
    All GPUs supported by the amdgpu kernel driver
[    10.425] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    10.425] (II) FBDEV: driver for framebuffer: fbdev
[    10.425] (II) VESA: driver for VESA chipsets: vesa
[    10.444] (II) AMDGPU(0): [KMS] Kernel modesetting enabled.
[    10.444] (WW) Falling back to old probe method for modesetting
[    10.445] (WW) Falling back to old probe method for fbdev
[    10.445] (II) Loading sub module "fbdevhw"
[    10.445] (II) LoadModule: "fbdevhw"
[    10.445] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    10.445] (II) Module fbdevhw: vendor="X.Org Foundation"
[    10.445]    compiled for 1.20.13, module version = 0.0.2
[    10.445]    ABI class: X.Org Video Driver, version 24.1
[    10.446] (II) AMDGPU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
[    10.446] (==) AMDGPU(0): Depth 24, (--) framebuffer bpp 32
[    10.446] (II) AMDGPU(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[    10.446] (==) AMDGPU(0): Default visual is TrueColor
[    10.446] (==) AMDGPU(0): RGB weight 888
[    10.446] (II) AMDGPU(0): Using 8 bits per RGB (8 bit DAC)
[    10.446] (--) AMDGPU(0): Chipset: "AMD Radeon(TM) Vega 10 Graphics" (ChipID = 0x15d8)
[    10.446] (II) Loading sub module "fb"
[    10.446] (II) LoadModule: "fb"
[    10.446] (II) Loading /usr/lib/xorg/modules/libfb.so
[    10.447] (II) Module fb: vendor="X.Org Foundation"
[    10.447]    compiled for 1.20.13, module version = 1.0.0
[    10.447]    ABI class: X.Org ANSI C Emulation, version 0.4
[    10.447] (II) Loading sub module "dri2"
[    10.447] (II) LoadModule: "dri2"
[    10.447] (II) Module "dri2" already built-in
[    10.587] (II) Loading sub module "glamoregl"
[    10.587] (II) LoadModule: "glamoregl"
[    10.587] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    10.593] (II) Module glamoregl: vendor="X.Org Foundation"
[    10.593]    compiled for 1.20.13, module version = 1.0.1
[    10.593]    ABI class: X.Org ANSI C Emulation, version 0.4
[    10.621] (II) AMDGPU(0): glamor X acceleration enabled on AMD Radeon(TM) Vega 10 Graphics (RAVEN, DRM 3.35.0, 5.4.0-91-generic, LLVM 12.0.0)
[    10.621] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[    10.621] (==) AMDGPU(0): TearFree property default: auto
[    10.621] (==) AMDGPU(0): VariableRefresh: disabled
[    10.621] (II) AMDGPU(0): KMS Pageflipping: enabled
[    10.621] (II) AMDGPU(0): Output eDP has no monitor section
[    10.621] (II) AMDGPU(0): Output HDMI-A-0 has no monitor section
[    10.639] (II) AMDGPU(0): EDID for output eDP
[    10.639] (II) AMDGPU(0): Manufacturer: AUO  Model: 20ec  Serial#: 0
[    10.639] (II) AMDGPU(0): Year: 2018  Week: 0
[    10.640] (II) AMDGPU(0): EDID Version: 1.4
[    10.640] (II) AMDGPU(0): Digital Display Input
[    10.640] (II) AMDGPU(0): 6 bits per channel
[    10.640] (II) AMDGPU(0): Digital interface is DisplayPort
[    10.640] (II) AMDGPU(0): Max Image Size [cm]: horiz.: 34  vert.: 19
[    10.640] (II) AMDGPU(0): Gamma: 2.20
[    10.640] (II) AMDGPU(0): No DPMS capabilities specified
[    10.640] (II) AMDGPU(0): Supported color encodings: RGB 4:4:4 
[    10.640] (II) AMDGPU(0): First detailed timing is preferred mode
[    10.640] (II) AMDGPU(0): Preferred mode is native pixel format and refresh rate
[    10.640] (II) AMDGPU(0): Display is continuous-frequency
[    10.640] (II) AMDGPU(0): redX: 0.563 redY: 0.338   greenX: 0.342 greenY: 0.576
[    10.640] (II) AMDGPU(0): blueX: 0.163 blueY: 0.133   whiteX: 0.313 whiteY: 0.329
[    10.640] (II) AMDGPU(0): Manufacturer's mask: 0
[    10.640] (II) AMDGPU(0): Supported detailed timing:
[    10.640] (II) AMDGPU(0): clock: 76.3 MHz   Image Size:  344 x 193 mm
[    10.640] (II) AMDGPU(0): h_active: 1366  h_sync: 1404  h_sync_end 1426 h_blank_end 1592 h_border: 0
[    10.640] (II) AMDGPU(0): v_active: 768  v_sync: 771  v_sync_end 777 v_blanking: 798 v_border: 0
[    10.640] (II) AMDGPU(0): Supported detailed timing:
[    10.640] (II) AMDGPU(0): clock: 50.9 MHz   Image Size:  344 x 193 mm
[    10.640] (II) AMDGPU(0): h_active: 1366  h_sync: 1404  h_sync_end 1426 h_blank_end 1592 h_border: 0
[    10.640] (II) AMDGPU(0): v_active: 768  v_sync: 771  v_sync_end 777 v_blanking: 798 v_border: 0
[    10.640] (II) AMDGPU(0): Unknown vendor-specific block 2
[    10.640] (II) AMDGPU(0): EDID (in hex):
[    10.640] (II) AMDGPU(0):    00ffffffffffff0006afec2000000000
[    10.640] (II) AMDGPU(0):    001c010495221378036ac59056579329
[    10.640] (II) AMDGPU(0):    22505400000001010101010101010101
[    10.640] (II) AMDGPU(0):    010101010101ce1d56e250001e302616
[    10.640] (II) AMDGPU(0):    360058c110000018df1356e250001e30
[    10.640] (II) AMDGPU(0):    2616360058c110000018000000000000
[    10.640] (II) AMDGPU(0):    00000000000000000000000000000002
[    10.640] (II) AMDGPU(0):    001048ff0f3c6e480f1b6e20202000a0
[    10.640] (II) AMDGPU(0): Printing probed modes for output eDP
[    10.640] (II) AMDGPU(0): Modeline "1366x768"x60.1   76.30  1366 1404 1426 1592  768 771 777 798 -hsync -vsync (47.9 kHz eP)
[    10.640] (II) AMDGPU(0): Modeline "1366x768"x40.0   50.87  1366 1404 1426 1592  768 771 777 798 -hsync -vsync (32.0 kHz e)
[    10.640] (II) AMDGPU(0): Modeline "1280x720"x60.1   76.30  1280 1404 1426 1592  720 771 777 798 -hsync -vsync (47.9 kHz e)
[    10.640] (II) AMDGPU(0): Modeline "1024x768"x60.1   76.30  1024 1404 1426 1592  768 771 777 798 -hsync -vsync (47.9 kHz e)
[    10.640] (II) AMDGPU(0): Modeline "800x600"x60.1   76.30  800 1404 1426 1592  600 771 777 798 -hsync -vsync (47.9 kHz e)
[    10.640] (II) AMDGPU(0): Modeline "640x480"x60.1   76.30  640 1404 1426 1592  480 771 777 798 -hsync -vsync (47.9 kHz e)
[    10.640] (II) AMDGPU(0): EDID for output HDMI-A-0
[    10.640] (II) AMDGPU(0): Output eDP connected
[    10.640] (II) AMDGPU(0): Output HDMI-A-0 disconnected
[    10.640] (II) AMDGPU(0): Using exact sizes for initial modes
[    10.640] (II) AMDGPU(0): Output eDP using initial mode 1366x768 +0+0
[    10.640] (II) AMDGPU(0): mem size init: gart size :bf7cf000 vram size: s:7ec0b000 visible:7ec0b000
[    10.640] (==) AMDGPU(0): DPI set to (96, 96)
[    10.640] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
[    10.640] (II) Loading sub module "ramdac"
[    10.640] (II) LoadModule: "ramdac"
[    10.640] (II) Module "ramdac" already built-in
[    10.640] (II) UnloadModule: "modesetting"
[    10.640] (II) Unloading modesetting
[    10.640] (II) UnloadModule: "fbdev"
[    10.640] (II) Unloading fbdev
[    10.640] (II) UnloadSubModule: "fbdevhw"
[    10.640] (II) Unloading fbdevhw
[    10.640] (II) UnloadModule: "vesa"
[    10.640] (II) Unloading vesa
[    10.641] (II) AMDGPU(0): [DRI2] Setup complete
[    10.641] (II) AMDGPU(0): [DRI2]   DRI driver: radeonsi
[    10.641] (II) AMDGPU(0): [DRI2]   VDPAU driver: radeonsi
[    10.691] (II) AMDGPU(0): Front buffer pitch: 5632 bytes
[    10.691] (II) AMDGPU(0): SYNC extension fences enabled
[    10.692] (II) AMDGPU(0): Present extension enabled
[    10.692] (==) AMDGPU(0): DRI3 enabled
[    10.692] (==) AMDGPU(0): Backing store enabled
[    10.692] (II) AMDGPU(0): Direct rendering enabled
[    10.711] (II) AMDGPU(0): Use GLAMOR acceleration.
[    10.711] (II) AMDGPU(0): Acceleration enabled
[    10.711] (==) AMDGPU(0): DPMS enabled
[    10.711] (==) AMDGPU(0): Silken mouse enabled
[    10.711] (II) AMDGPU(0): Set up textured video (glamor)
[    10.723] (II) Initializing extension Generic Event Extension
[    10.723] (II) Initializing extension SHAPE
[    10.723] (II) Initializing extension MIT-SHM
[    10.723] (II) Initializing extension XInputExtension
[    10.724] (II) Initializing extension XTEST
[    10.724] (II) Initializing extension BIG-REQUESTS
[    10.724] (II) Initializing extension SYNC
[    10.724] (II) Initializing extension XKEYBOARD
[    10.724] (II) Initializing extension XC-MISC
[    10.725] (II) Initializing extension SECURITY
[    10.725] (II) Initializing extension XFIXES
[    10.725] (II) Initializing extension RENDER
[    10.725] (II) Initializing extension RANDR
[    10.725] (II) Initializing extension COMPOSITE
[    10.725] (II) Initializing extension DAMAGE
[    10.725] (II) Initializing extension MIT-SCREEN-SAVER
[    10.725] (II) Initializing extension DOUBLE-BUFFER
[    10.726] (II) Initializing extension RECORD
[    10.726] (II) Initializing extension DPMS
[    10.726] (II) Initializing extension Present
[    10.726] (II) Initializing extension DRI3
[    10.726] (II) Initializing extension X-Resource
[    10.726] (II) Initializing extension XVideo
[    10.727] (II) Initializing extension XVideo-MotionCompensation
[    10.727] (II) Initializing extension SELinux
[    10.727] (II) SELinux: Disabled on system
[    10.727] (II) Initializing extension GLX
[    23.754] (II) AIGLX: Loaded and initialized radeonsi
[    23.754] (II) GLX: Initialized DRI2 GL provider for screen 0
[    23.754] (II) Initializing extension XFree86-VidModeExtension
[    23.755] (II) Initializing extension XFree86-DGA
[    23.755] (II) Initializing extension XFree86-DRI
[    23.755] (II) Initializing extension DRI2
[    23.766] (II) AMDGPU(0): Setting screen physical size to 361 x 203

由于问题再次出现,我什至无法从计算机进入睡眠状态恢复。有人可以帮我弄清楚发生了什么吗?

multiple-monitors
  • 1 个回答
  • 322 Views
Martin Hope
mikemtnbikes
Asked: 2021-08-27 11:15:00 +0800 CST

登录屏幕问题:需要杀死第一个 lightdm 才能使 X 会话正常工作

  • 0

我正在运行 MATE 20.04,每次重新启动时都会出现问题。而不是获取 lightdm 登录屏幕

  1. 当我设置 grub 选项“静音”时,我得到一个空白屏幕(全黑但打开)
  2. 当我删除静音选项时,我收到以下消息
    Loading, please wait..
    Starting version 245.4_ubuntu3.11
    Begin: Loading essential drivers ... done.
    Begin: Running /scripts/init-premount
    
    屏幕变为空白,然后重新显示上述消息

此时,如果我尝试使用本地术语(Ctl-Fn-F1),我没有运气。但是,如果我 ssh 进入机器并杀死 lightdm,则会出现登录屏幕。这里有更多细节

  > [machine ~] $ ps aux |grep lightdm
  > root        1173  0.0  0.0 232332  7484 ?        Ssl  14:45   0:00 /usr/sbin/lightdm
  > root        1225  0.2  0.6 1346752 67728 tty7    Ssl+ 14:45   0:00 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  > user1       1854  0.0  0.0   9032   724 pts/0    S+   14:46   0:00 grep lightdm
  > [machine ~] $ sudo kill 1173
  > [sudo] password for user1:
  > [machine ~] $ ps aux |grep lightdm
  > root        1925  0.4  0.0 232332  7328 ?        Ssl  14:47   0:00 /usr/sbin/lightdm
  > root        1930 12.8  0.9 1497312 96312 tty7    Ssl+ 14:47   0:00 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  > root        1955  0.2  0.0 159972  8236 ?        Sl   14:47   0:00 lightdm --session-child 17 20
  > lightdm     1959  5.0  0.0  18836  9948 ?        Ss   14:47   0:00 /lib/systemd/systemd --user
  > lightdm     1960  0.0  0.0 169680  4188 ?        S    14:47   0:00 (sd-pam)
  > lightdm     1969  4.0  0.1 358024 18308 ?        S<sl 14:47   0:00 /usr/bin/pulseaudio --daemonize=no --log-target=journal
  > lightdm     1972  0.0  0.0 166156  4764 ?        Sl   14:47   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
  > lightdm     1975  0.0  0.0   2608   540 ?        Ss   14:47   0:00 /bin/sh /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/slick-greeter
  > lightdm     1976 25.2  0.4 601636 48404 ?        Sl   14:47   0:01 /usr/sbin/slick-greeter
  > lightdm     1977  0.5  0.0   7464  4608 ?        Ss   14:47   0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
  > lightdm     1983  0.0  0.0 156092  5376 ?        Sl   14:47   0:00 /usr/libexec/dconf-service
  > lightdm     2011  0.0  0.0 305748  6592 ?        Sl   14:47   0:00 /usr/libexec/at-spi-bus-launcher --launch-immediately
  > lightdm     2016  0.0  0.0   7332  4144 ?        S    14:47   0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
  > lightdm     2017  0.0  0.0 239704  7512 ?        Ssl  14:47   0:00 /usr/libexec/gvfsd
  > lightdm     2022  0.0  0.0 312800  6144 ?        Sl   14:47   0:00 /usr/libexec/gvfsd-fuse /run/user/110/gvfs -f -o big_writes
  > root        2056  0.0  0.0  12560  6200 ?        S    14:47   0:00 lightdm --session-child 13 20
  > lightdm     2058  0.5  0.0 162828  7668 ?        Sl   14:47   0:00 /usr/libexec/at-spi2-registryd --use-gnome-session
  > user1       2064  0.0  0.0   9032   664 pts/0    S+   14:47   0:00 grep lightdm

另一个“修复”是启动进入安全模式,然后通过“恢复”选项继续。登录显示没有问题。

首先,这是怎么回事?

其次,为什么我不能通过 Ctl-Fn-F1 访问条款?

非常感谢。

更新:

  • 在引导内核时使用“nomodeset”可以避免这个问题。
    • 此参数也用于恢复模式,并解释该方法为何有效
    • 不幸的是,如果我使用这个“解决方案”,当我从睡眠中恢复时会出现黑屏
  • 收到有关未找到我的外部显示器的通知
    • 尝试使用插入的外部显示器启动,我使用默认设置获得登录屏幕(我不需要使用 nomodeset)
    • 需要看看简历下一步是否有效。
    • 如果我在上一个会话中使用外接显示器,登录屏幕似乎存在问题。我怀疑这意味着它正在寻找第二个显示器,找不到它,所以它挂起。
xorg
  • 1 个回答
  • 416 Views
Martin Hope
mikemtnbikes
Asked: 2017-11-17 11:21:29 +0800 CST

如何使用 CalDav 在 Evolution 中同步任务和备忘录

  • 1

我试图弄清楚如何将进化的“任务”和/或“备忘录”功能与运行 NextCloud 的远程服务器同步。但是,我在本地创建的任务和我直接在远程服务器上创建的任务都不会相互同步。在进化中,我正在使用以下设置设置一个新的任务列表。

  • 类型:网上
  • 网址:https ://CLOUDSERVICE.com/remote.php/dav/calendars/USER/MYCALENDAR/
  • 使用安全连接:x

据我了解,CalDav 日历可以包含 TODO 项目,因此我正在尝试同步到日历 MYCALENDAR,我可以通过进化的“日历”功能同步到该日历。

sync
  • 1 个回答
  • 3129 Views
Martin Hope
mikemtnbikes
Asked: 2016-05-07 18:06:24 +0800 CST

如何阻止自己在周末登录?

  • 2

我想知道是否有人在周末编写过阻止远程访问(特别是我通过 ssh 连接在本地 linux 机器上通过 alpine 访问的 linux 电子邮件服务器)的 cron 脚本?我不想依靠自己的自我控制,也不想在邮件服务器上拥有 root 权限。

我可以想象有一个脚本将我的密码更改为随机字符串,然后在星期一早上将其设置回来,但这似乎我必须在某处未加密我的密码。或者,加密我的 ssh 密钥?

如果您有见解或建议,我将不胜感激。

cron
  • 2 个回答
  • 80 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

  • 主页
  • 问题
    • 最新
    • 热门
  • 标签
  • 帮助

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve