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 / 问题

问题[segmentation-fault](ubuntu)

Martin Hope
DEBAGNIK KAR
Asked: 2020-12-16 20:45:43 +0800 CST

如何将 tracegraph 安装到 ubuntu 20.04 LTS

  • 1

tracegraph202 是一个非常古老且过时的工具,并且与 Linux 不兼容,但我的大学仍然认为让学生安装它是个好主意。我尝试从这里安装它,这里和这里都没有在我的最终工作。请帮忙

compatibility libraries segmentation-fault 12.10 20.04
  • 1 个回答
  • 878 Views
Martin Hope
Sergjo
Asked: 2020-10-06 07:02:38 +0800 CST

升级到 Ubuntu 20.04.1 后出现 xorg 段错误 - 如何继续?

  • 3

我刚刚升级到 Ubuntu 20.04.1,重新启动后出现黑屏,光标闪烁(但无法输入)。

来自Xorg.0.log:

[    10.307] (II) Loading sub module "fb"
[    10.307] (II) LoadModule: "fb"
[    10.310] (II) Loading /usr/lib/xorg/modules/libfb.so
[    10.311] (II) Module fb: vendor="X.Org Foundation"
[    10.311]    compiled for 1.20.8, module version = 1.0.0
[    10.311]    ABI class: X.Org ANSI C Emulation, version 0.4
[    10.311] (II) UnloadModule: "fbdev"
[    10.311] (II) Unloading fbdev
[    10.311] (II) UnloadSubModule: "fbdevhw"
[    10.311] (II) Unloading fbdevhw
[    10.311] (II) UnloadModule: "vesa"
[    10.311] (II) Unloading vesa
[    10.311] (EE) 
[    10.311] (EE) Backtrace:
[    10.312] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5580989b311c]
[    10.312] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fdec4e5841f]
[    10.313] (EE) 2: ? (?+0x0) [0x0]
[    10.313] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    10.313] (EE) 3: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fdec46fb850]
[    10.313] (EE) 4: ? (?+0x0) [0x55809a1b9f90]
[    10.313] (EE) 
[    10.313] (EE) Segmentation fault at address 0x0
[    10.313] (EE) 
Fatal server error:
[    10.313] (EE) Caught signal 11 (Segmentation fault). Server aborting

以下是文件开头的一些版本信息:

[    10.224] Build Operating System: Linux 4.15.0-115-generic x86_64 Ubuntu
[    10.224] Current Operating System: Linux abc-ThinkPad-E485 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64
[    10.224] Kernel command line: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ivrs_ioapic[32]=00:14.0 ivrs_ioapic[33]=00:00.1 iommu=pt processor.max_cstate=5 vt.handoff=7
[    10.224] Build Date: 04 September 2020  01:34:27PM
[    10.224] xorg-server 2:1.20.8-2ubuntu2.4 (For technical support please see http://www.ubuntu.com/support) 
[    10.225] Current version of pixman: 0.38.4

任何想法如何解决它/获取更多信息?我不介意简单地降级 ubuntu,但我读到降级也不一定是个好主意。

我发现了这个错误,它看起来有点相关。但我不知道如何恢复台面,或者这是否真的是原因。

xorg segmentation-fault 20.04
  • 1 个回答
  • 1474 Views
Martin Hope
Dalarielus
Asked: 2020-09-11 07:35:44 +0800 CST

CPU升级后分段故障/无法启动?

  • 0

我的机器是运行 Ubuntu Server 20.04 的 HP ProDesk 400 G4 SFF。

它在原来的 Intel i5-6500 CPU 上运行良好,但升级到 i7-6700 后系统将不再启动。

我试过进入救援模式和紧急模式,但它们都不会真正启动系统。有任何想法吗?

编辑:我也无法从 USB 驱动器上的安装媒体启动。以下是启动失败的屏幕截图:

分段故障

server boot segmentation-fault intel-cpu
  • 1 个回答
  • 581 Views
Martin Hope
JJD
Asked: 2020-08-05 09:50:19 +0800 CST

包更新/台面分段错误后 Ubuntu 18.04.4 启动卡住

  • 2

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 没有启动。

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

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

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

基本上就是这样。

boot xorg segmentation-fault mesa 18.04
  • 1 个回答
  • 1504 Views
Martin Hope
Михаил Ребров
Asked: 2019-11-11 13:56:02 +0800 CST

pop-theme 导致 gnome-control-center 分段错误

  • 5

Ubuntu 19.10
侏儒 3.28

我正在尝试运行gnome-control-center

结果:

分段错误(核心转储)

  • 清除 gnome-control-center .cache 和 .config
  • 删除所有 gnome 扩展
  • 安装了所有更新
  • 重启

没有改变...

     > coredumpctl info:

          PID: 12246 (gnome-control-c)
          UID: 1000 (michaeldl)
          GID: 1000 (michaeldl)
       Signal: 11 (SEGV)
    Timestamp: Sun 2019-11-10 23:23:21 MSK (1h 6min ago)
 Command Line: gnome-control-center
   Executable: /usr/bin/gnome-control-center
Control Group: /user.slice/user-1000.slice/[email protected]/gnome-shell-x11.service
         Unit: [email protected]
    User Unit: gnome-shell-x11.service
        Slice: user-1000.slice
    Owner UID: 1000 (michaeldl)
      Boot ID: 4a24792e63014ae2904ad4e50987a50c
   Machine ID: ef03f98c351a4bb19f7d0ca6b14695c6
     Hostname: michaeldl
      Storage: /var/lib/systemd/coredump/core.gnome-control-c.1000.4a24792e63014ae2904ad4e50987a50c.12246.1573417401000000.lz4
   Message: Process 12246 (gnome-control-c) of user 1000 dumped core.

            Stack trace of thread 12246:
            #0  0x00007f34a3155e1e gtk_container_add (libgtk-3.so.0)
            #1  0x000055c367493ba5 n/a (gnome-control-center)
            #2  0x00007f34a3830546 n/a (libgobject-2.0.so.0)
            #3  0x00007f34a3832278 g_object_new_valist (libgobject-2.0.so.0)
            #4  0x00007f34a38325cd g_object_new (libgobject-2.0.so.0)
            #5  0x000055c367452676 n/a (gnome-control-center)
            #6  0x00007f34a382d7ef g_cclosure_marshal_VOID__STRINGv (libgobject-2.0.so.0)
            #7  0x00007f34a382a936 n/a (libgobject-2.0.so.0)
            #8  0x00007f34a384736c g_signal_emit_valist (libgobject-2.0.so.0)
            #9  0x00007f34a38479b3 g_signal_emit (libgobject-2.0.so.0)
            #10 0x000055c367450787 n/a (gnome-control-center)
            #11 0x00007f34a382dde3 g_cclosure_marshal_VOID__OBJECTv (libgobject-2.0.so.0)
            #12 0x00007f34a382a936 n/a (libgobject-2.0.so.0)
            #13 0x00007f34a384736c g_signal_emit_valist (libgobject-2.0.so.0)
            #14 0x00007f34a38479b3 g_signal_emit (libgobject-2.0.so.0)
            #15 0x00007f34a382a936 n/a (libgobject-2.0.so.0)
            #16 0x00007f34a384736c g_signal_emit_valist (libgobject-2.0.so.0)
            #17 0x00007f34a3847fa9 g_signal_emit_by_name (libgobject-2.0.so.0)
            #18 0x000055c367450f49 cc_panel_list_set_active_panel (gnome-control-center)
            #19 0x000055c36745316f n/a (gnome-control-center)
            #20 0x00007f34a3830546 n/a (libgobject-2.0.so.0)
            #21 0x00007f34a3832278 g_object_new_valist (libgobject-2.0.so.0)
            #22 0x00007f34a38325cd g_object_new (libgobject-2.0.so.0)
            #23 0x000055c3674535ac cc_window_new (gnome-control-center)
            #24 0x000055c36744cfc3 n/a (gnome-control-center)
            #25 0x00007f34a382a936 n/a (libgobject-2.0.so.0)
            #26 0x00007f34a384736c g_signal_emit_valist (libgobject-2.0.so.0)
            #27 0x00007f34a38479b3 g_signal_emit (libgobject-2.0.so.0)
            #28 0x00007f34a3952312 g_application_register (libgio-2.0.so.0)
            #29 0x00007f34a39526ee n/a (libgio-2.0.so.0)
            #30 0x00007f34a3952a72 g_application_run (libgio-2.0.so.0)
            #31 0x000055c36744c639 main (gnome-control-center)
            #32 0x00007f34a15c71e3 __libc_start_main (libc.so.6)
            #33 0x000055c36744c84e _start (gnome-control-center)

            Stack trace of thread 12255:

有任何想法吗?..

UPD:
删除带有依赖项的 gnome-control-center 并重新安装...
没有任何改变...

gnome gnome-control-center segmentation-fault
  • 2 个回答
  • 3228 Views
Martin Hope
Max
Asked: 2019-02-22 01:49:49 +0800 CST

qt-opensource-linux-x64-5.12.1.run - 给出分段错误

  • 0

我的操作系统 - Ubuntu 16.04。我已经下载了 qt-opensource-linux-x64-5.12.1.run。我从终端运行它。它给出了分段错误。

qt segmentation-fault offline
  • 1 个回答
  • 333 Views
Martin Hope
Rubi Shnol
Asked: 2018-11-02 11:25:18 +0800 CST

与相机 IPC 相关的 Segfaults

  • 0

我不断收到这些奇怪的 Firefox 段错误。每次我在挂起后打开笔记本电脑的盖子时,Firefox 都会冻结,只有强制退出有帮助。

这已经在几周前开始了。

当我做dmesg | grep segfault,我收到与“Cameras IPC”相关的错误。

这可能是什么?

Firefox 会尝试访问我的网络摄像头吗?

以下是错误消息:

[129627.988672] firefox[25135]: segfault at 0 ip 00007
fd23cf4398b sp 00007ffdf3695598 error 6 in libxul.so[7fd23a7e9000+653b000]
[134905.990042] Chrome_~dThread[26745]: segfault at 0 ip 00007ff22ed607bd sp 00007ff2408c0b00 error 6 in libxul.so[7ff22dfe9000+653b000]
[170542.318548] Chrome_~dThread[22231]: segfault at 0 ip 00007f4935b607bd sp 00007f49476f9b00 error 6 in libxul.so[7f4934de9000+653b000]
[170542.345143] Cameras IPC[22624]: segfault at 0 ip 0000561b1bfec9fb sp 00007f826c48e870 error 6 in firefox[561b1bfe7000+32000]
[170542.345340] Chrome_~dThread[22435]: segfault at 0 ip 00007f8535a607bd sp 00007f85476b8b00 error 6 in libxul.so[7f8534ce9000+653b000]
[220194.968631] Chrome_~dThread[24003]: segfault at 0 ip 00007f978f7607bd sp 00007f97a1352b00 error 6
[220194.968634] Cameras IPC[24049]: segfault at 0 ip 000056030e8429fb sp 00007f5fc9962870 error 6
[220194.968636] Cameras IPC[30094]: segfault at 0 ip 000055cb1923c9fb sp 00007f3446b9f870 error 6
[220194.968639] Cameras IPC[9936]: segfault at 0 ip 00005603c8aa39fb sp 00007f80cd6bc870 error 6

这是信息:

Firefox version 63.0
Ubuntu 18.04.1 LTS
NVidia driver metapackage from nvidia-driver-390
firefox suspend camera freeze segmentation-fault
  • 1 个回答
  • 854 Views
Martin Hope
Smoksul
Asked: 2018-10-17 10:04:17 +0800 CST

Evince 产生分段错误

  • 3

最近我在我的笔记本电脑(Dell Precision M4700,16GB RAM)上安装了 Ubuntu 18.04.1,目前它非常纯净。问题是 Evince 3.30.0 在启动时会产生分段错误(核心转储)。自从安装了系统并且清除和重新安装(也通过 Synaptic)没有帮助后,它就发生了。任何想法如何使它工作?

我进入了

~/.local/share/gnome-shell 

检查扩展文件夹中的内容 - 它发生了,没有这样的文件夹(根本没有文件夹),/gnome-shell 中的 'ls' 产生:

application_state

切换到另一个(新创建的)用户并在那里运行 Evince 会产生相同的结果。

运行 sudo debsums -s 提供的输出:

debsums: changed file /usr/share/X11/xkb/symbols/pl (from xkb-data package)

这是我手动编辑的文件。将其替换为原始文件(并删除我创建的新用户)我从终端中运行 evince 获得了更多输出:

Attempting to read the recently used resources file at 
'/home/january/.local/share/recently-used.xbel', but the parser failed:
Failed to open file “/home/january/.local/share/recently-used.xbel”: 
Permission denied.
Segmentation fault (core dumped)

该文件对我的用户有读写权限,但对我的组没有权限。我编辑了这些权限,为我的小组提供读写权限,现在Segmentation fault就像我之前运行 Evince 时一样。

我还使用 Synaptic 再次清除了 Evince 以安装版本3.28.2-1(通过 Synaptic)。首先,当我Apply尝试再次安装 Evince 时使用 GUI 按钮时遇到错误:

E: Unable to correct problems, you have held broken packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Unable to lock the download directory.

当我选择Edit->Apply Marked Changes. 运行 Evince 时重新安装仍会产生 Seg.fault。

运行sudo evince我得到:

No protocol specified
Unable to init server: Could not connect: Connection refused
Cannot parse arguments: Cannot open display: 

由于事情是随机发生的,有时我设法从 GUI 中的 evince 中得到一个错误(你会称之为飞溅吗?),抱歉它太大了,我想包含所有可能的数据。

https://i.imgur.com/Q8zHcV0.jpg

fsck在恢复根命令行中运行没有产生错误。

几天前我做了memtest,然后我做了一个fsck,收到了这个结果:

年长者:https ://i.imgur.com/ri3oAmP.jpg

较新:https ://i.imgur.com/tsQ3dSY.jpg

evince segmentation-fault
  • 2 个回答
  • 2616 Views
Martin Hope
thezin
Asked: 2018-05-16 07:24:14 +0800 CST

腻子分段错误

  • 1

我刚刚使用sudo apt-get install putty命令安装了 PuTTY。

当我尝试运行它时,我立即收到Segmentation fault (core dumped)错误消息。

我怎样才能解决这个问题?

segmentation-fault putty 17.10
  • 1 个回答
  • 1530 Views
Martin Hope
thebunnyrules
Asked: 2018-02-21 21:04:19 +0800 CST

提交崩溃报告后,我在哪里可以获得 apport 追溯信息

  • 1

我在 gnome-shell 中遇到了很多 segv 崩溃,虽然 apport 窗口有很多信息,但它对用户不是很友好(窗口非常小,无法搜索,无法将副本保存到文本文件等) .

有没有办法可以直接从终端访问可用于申请的信息?gnome-shell 是否将回溯日志保存在某处?

我知道 /var/log 中有一个用于 apport 的日志文件,但该日志文件没有提供几乎相同级别的详细信息。

gnome command-line gnome-shell segmentation-fault apport
  • 1 个回答
  • 246 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