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-18533

JJD's questions

Martin Hope
JJD
Asked: 2020-10-12 11:19:07 +0800 CST

Ubuntu 20.04.1 升级失败/错误 Dist-upgrade failed: 'Broken packages after upgrade: colord'

  • 6

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

$ sudo do-release-upgrade

这失败如下:

...

无法计算升级

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

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

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

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

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

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

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

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

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

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

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

问题

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

有关的

  • 包更新/台面分段错误后 Ubuntu 18.04.4 启动卡住
  • 由于被保留的软件包,似乎无法从 18.04 升级到 20.04:libsensors4、libsensors-config、colord
  • libsensors5 或 libsensors-config 升级问题
  • 从 18.04 升级到 20.04 失败...
package-management apt mesa do-release-upgrade 20.04
  • 2 个回答
  • 5511 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
JJD
Asked: 2014-09-20 05:02:33 +0800 CST

桌面条目未出现在 Unity 启动器中

  • 2

我为自定义 QGIS 安装创建了一个.desktop条目。出于某种原因,Unity 启动器和Kupfer拒绝为该条目编制索引——它没有显示。~/.local/share/applications

这是 的内容~/.local/share/applications/qgis-custom.desktop。我遗漏了翻译。

[Desktop Entry]
Type=Application
Name=QGIS Desktop HEAD
Version=1.0
GenericName=Geographic Information System
Icon=qgis
TryExec=env LD_LIBRARY_PATH=/home/jjd/bin/qgis/lib /home/jjd/bin/qgis/bin/qgis
Exec=env LD_LIBRARY_PATH=/home/jjd/bin/qgis/lib /home/jjd/bin/qgis/bin/qgis %F
Terminal=false
StartupNotify=false
Categories=Qt;Education;Science;Geography;
MimeType=application/x-qgis-project;image/tiff;image/jpeg;image/jp2;application/x-raster-aig;application/x-raster-ecw;application/x-raster-mrsid;application/x-mapinfo-mif;application/x-esri-shape;
Keywords=map;globe;postgis;wms;wfs;ogc;osgeo

在以前的问题中,我发现LD_LIBRARY_PATH必须导出。当我从 shell 启动应用程序时,应用程序成功启动。

unity
  • 1 个回答
  • 717 Views
Martin Hope
JJD
Asked: 2014-08-08 02:25:11 +0800 CST

如何为位于用户空间的应用程序创建桌面条目?

  • 0

我将最新的 QGIS 资源编译成~/bin/qgis. 我可以从运行的命令行启动应用程序~/bin/qgis/bin/qgis。现在我想要应用程序启动器条目。所以我复制了.desktopQGIS distribution安装的文件:

cp /usr/share/applications/qgis.desktop ~/.local/share/applications

接下来我重命名它:

cd ~/.local/share/applications
mv qgis.desktop qgis-custom.desktop

接下来,我编辑了文件TryExec中的路径Exec:

[Desktop Entry]
Type=Application
Name=QGIS Desktop Latest
Version=1.0
GenericName=Geographic Information System
GenericName[ar]=نظام المعلومات الجغرافي
# other translations omitted for brevity
GenericName[uz]=Geografik axborot tizimi
Icon=qgis
TryExec=/home/jjd/bin/qgis/bin/qgis
Exec=/home/jjd/bin/qgis/bin/qgis %F
Terminal=false
StartupNotify=false
Categories=Qt;Education;Science;Geography;
MimeType=application/x-qgis-project;image/tiff;image/jpeg;image/jp2;application/x-raster-aig;application/x-raster-ecw;application/x-raster-mrsid;application/x-mapinfo-mif;application/x-esri-shape;
Keywords=map;globe;postgis;wms;wfs;ogc;osgeo;

(旧的 .desktop 文件)

最后我尝试从 Unity 启动器启动它。什么都没有发生....
我记得有一点不同,那就是我必须在 shell 中导出库路径:

export LD_LIBRARY_PATH=$HOME/bin/qgis/lib

我猜这是应用程序启动器条目所缺少的。

unity
  • 1 个回答
  • 1778 Views
Martin Hope
JJD
Asked: 2014-07-30 01:32:12 +0800 CST

Ubuntu 版本从 13.10 升级到 14.04 失败 - 登录失败

  • 0

升级 Ubuntu

从 Ubuntu 13.10 升级。到 14 月 04 日。我跑了sudo do-release-upgrade。第一次尝试失败,我在错误日志中发现了以下消息:

/var/log/dist-upgrade/20140724-1529/main.log:

ERROR Dist-upgrade failed: 'The package 'postgresql-9.3-postgis-2.1' is marked 
for removal but it is in the removal blacklist.'

成功卸载软件包后,我重新运行升级。

最初的问题

我重新启动了计算机,然后它停止启动并显示以下屏幕输出:

* Starting nginx nginx
speech-dispatcher disabled; edit /etc/default/speech-dispatcher
Starting VirtualBox kernel modules ...done.
saned disabled; edit /etc/default/saned
 * Restoring resolver state
 * Starting web server apache2
 *

尝试启动用户界面

从控制台我尝试启动 UI running:sudo service lightdm start失败并显示消息:

作业启动失败

查看/var/log/lightdm/我发现以下错误:

x-0-greeter.log:

WARNING: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0 \
  /2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden.
This likely means that your installation is broken
Try running the command
gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache \
  to make thinks work again for the time being
WARNING: Error loading image 'file:///usr/share/themes/Ambiance/gtk-3.0/assets/entry.png':
  Format der Bilddatei unbekannt
WARNING: Error loading image 'file:///usr/share/themes/Ambiance/gtk-3.0/assets/ \
  entry-disabled.png': Format der Bilddatei unbekannt
/usr/sbin/unity-greeter: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: 
  undefined symbol: cairo_surface_set_device_scale
** (gnome-settings-daemon:2614): WARNING **: Could not open X display

..

x-0.log:

Loading extension GLX
modprobe: ERROR: ../libkmod/libkmod-module.c:809 kmod_module_insert_module() could 
  not find module by name='nvidia_311'
modprobe: ERROR: could not insert 'nvidia_331': Function not implemented
error setting MTRR (base = 0xf3000000, size = 0x00e00000, type = 1) Invalid argument (22)

显卡驱动

几周前,我切换到另一个图形驱动程序,如此处所述。
正如这里所建议的,我从他们的网站上下载了我的显卡的当前 NVidia 驱动程序并运行以下命令并运行:

sudo ./NVIDIA-Linux-x86_64-331.79.run

但是,安装会停止并显示以下消息:

发行版提供的预安装脚本失败!继续安装吗?[是] [否]

我暂时选择NO了。

运行 apt-get

接下来我决定跑步sudo apt-get -f install。

在某件事的中间,它停止并显示以下消息:

Setting up nvidia-331 (331.38-0ubuntu7) ...

Configuration file '/etc/init/nvidia-persistenced.conf'
 ==> Deleted (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ? Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
 *** nvidia-persistenced,conf (Y/I/N/O/D/Z) [default=N] ?

我之所以选择Y,是因为我对安装的内容并不幸运,正如您可能猜到的那样……

部分成功

重新启动 UI 启动的系统!
但是,当我在登录字段中输入密码时,没有任何反应。此外,登录字段看起来有些奇怪 - 用户名几乎不可读 - 好像缺少背景图片(见屏幕照片)。

Ubuntu登录掩码

然后我再次运行sudo apt-get install --reinstall ubuntu-session并重新启动。现在我可以登录了。

仍然存在的问题:窗口管理器似乎已损坏。我看不到 Unity 破折号、窗口菜单栏……

没有 Unity 的 Ubuntu 桌面

显卡驱动噩梦第二部分

同时,我决定不顾警告安装之前提到的驱动程序:

sudo ./NVIDIA-Linux-x86_64-331.79.run

现在,系统启动:我可以看到一秒钟的 shell 登录提示,但没有 UI,并且屏幕保持黑色。当我按下电源按钮时,系统关闭(我可以看到例程)。我无法再通过Ctrl++访问Altshell F1。好像我搞砸了:(

按照bain的建议,通过将属性添加text到内核参数来恢复到以前的状态(没有菜单栏)。

/var/log/syslog 中的错误或警告

/var/日志/系统日志:

Jul 30 09:28:23 E6500 kernel: [  186.883606] traps: compiz[2666] trap int3 ip:7f97c4279c13 sp:7fff48a43bf0 error:0
Jul 30 09:28:25 E6500 gnome-session[2560]: WARNING: Application 'compiz.desktop' killed by signal 5
Jul 30 09:28:25 E6500 gnome-session[2560]: WARNING: App 'compiz.desktop' respawning too quickly
Jul 30 09:28:25 E6500 gnome-session[2560]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Jul 30 09:28:26 E6500 kernel: [  189.550661] traps: compiz[3059] trap int3 ip:7fb39f46ec13 sp:7fff38ee5170 error:0
Jul 30 09:28:26 E6500 gnome-session[2560]: WARNING: App 'compiz.desktop' respawning too quickly
Jul 30 09:28:26 E6500 gnome-session[2560]: WARNING: Application 'compiz.desktop' killed by signal 5
Jul 30 09:28:26 E6500 gnome-session[2560]: WARNING: App 'compiz.desktop' respawning too quickly
unity
  • 2 个回答
  • 3989 Views
Martin Hope
JJD
Asked: 2014-06-13 01:16:40 +0800 CST

如何在 Ubuntu 13.10 中自动启动 Kupfer?

  • 0

我在 Ubuntu 13.10 上从源代码构建了Kupfer并将其安装到./local. 在我检查的首选项Start automatically on login中。

Kupfer 偏好设置

但是,Kupfer 不会自动启动。

中的桌面文件~/.local/share/applications/kupfer.desktop如下所示:

[Desktop Entry]
Version=1.0
Name=Kupfer
Name[cs]=Kupfer
Name[da]=Kupfer
Name[de]=Kupfer
Name[el]=Kupfer
Name[es]=Kupfer
Name[eu]=Kupfer
Name[fr]=Kupfer
Name[gl]=Kupfer
Name[hu]=Kupfer
Name[it]=Kupfer
Name[ko]=쿠퍼
Name[nb]=Kupfer
Name[nl]=Kupfer
Name[pl]=Kupfer
Name[pt]=Kupfer
Name[pt_BR]=Kupfer
Name[ru]=Kupfer
Name[sl]=Kupfer
Name[sv]=Kupfer
Name[tr]=Kupfer
Name[zh_CN]=Kupfer
GenericName=Application Launcher
GenericName[ca]=Llançador d'aplicació
GenericName[cs]=Spouštěč aplikací
GenericName[da]=Programopstarter
GenericName[de]=Anwendungsstarter
GenericName[el]=Εκκινητής εφαρμογής
GenericName[es]=Lanzador de aplicaciones
GenericName[eu]=Aplikazioen abiarazlea
GenericName[fr]=Lanceur d'applications
GenericName[gl]=Iniciador de aplicativos
GenericName[hu]=Alkalmazásindító
GenericName[it]=Lanciatore di applicazioni
GenericName[ko]=응용 프로그램 실행 아이콘
GenericName[nb]=Programstarter
GenericName[nl]=Programmastarter
GenericName[pl]=Aktywator programów
GenericName[pt]=Lançador de Aplicações
GenericName[pt_BR]=Lançador de aplicativos
GenericName[ru]=Средство запуска приложений
GenericName[sl]=Zaganjalnik programov
GenericName[sv]=Programstartare
GenericName[tr]=Uygulama Çalıştırıcı
GenericName[zh_CN]=程序启动器
Comment=Convenient command and access tool for applications and documents
Comment[cs]=Nástroj pro pohodlné provádění příkazů a přístup k aplikacím a dokumentům
Comment[da]=Nemt kommando- og adgangsværktøj til programmer og dokumenter
Comment[de]=Praktisches Befehls- und Zugriffswerkzeug für Anwendungen und Dokumente
Comment[el]=Βολικό εργαλείο εντολών και πρόσβασης για εφαρμογές και έγγραφα
Comment[es]=Herramienta para acceso y manejo de aplicaciones y documentos
Comment[eu]=Komando eta atzipen tresna egokia aplikazio eta dokumentuentzat
Comment[fr]=Outil pratique pour accéder à des documents et lancer des applications
Comment[gl]=Ferramenta cómoda para controlar e acceder a aplicativos e documentos
Comment[hu]=Kényelmes parancs és hozzáférési eszköz az alkalmazásokhoz és dokumentumokhoz
Comment[it]=Comodo comando e strumento di accesso per applicazioni e documenti
Comment[ko]=편리하게 응용프로그램이나 문서에 접근하고 명령을 내릴 수 있는 도구
Comment[nb]=Praktiskt kommandoverktøy for programmer og dokumenter 
Comment[nl]=Handige opdracht- en toegangshulp voor programma's en documenten
Comment[pl]=Wygodne narzędzie do uruchamiania programów i otwierania dokumentów
Comment[pt]=Ferramenta conveniente para acesso e gestão de aplicações e documentos
Comment[pt_BR]=Uma conveniente ferramenta de comando e acesso para aplicativos e documentos
Comment[ru]=Удобный инструмент для быстрого доступа к программам и документам
Comment[sl]=Prikladno orodje za izvajanje ukazov in dostopa do programov in dokumentov
Comment[sv]=Praktiskt kommandoprogram för åtkomst av program och dokument
Comment[zh_CN]=方便的命令和操作程序或文档的工具
Icon=kupfer
Exec=python /home/user/.local/share/kupfer/kupfer.py %F
Type=Application
Categories=Utility;
StartupNotify=true
X-UserData=$CONFIG/kupfer;$DATA/kupfer;$CACHE/kupfer
Terminal=false
13.10
  • 1 个回答
  • 367 Views
Martin Hope
JJD
Asked: 2014-05-25 12:29:43 +0800 CST

如何在 Kupfer 中索引系统设置?

  • 4

我正在运行Ubuntu 14.04。并安装了Kupfer 208。

库普费尔

出于某种原因,我无法从Display或Appearance等系统设置中搜索和启动应用程序。Unity启动器会找到所有这些。

系统设置

我查看了设置和插件列表,但找不到如何索引System Setting。

launcher
  • 1 个回答
  • 780 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