有谁知道是否有ms-office-online与 AUR ms-office-online 20.1.0-2中的软件包等效的 Ubuntu ？
我有一台戴尔 XPS 9370，众所周知它只有一个摄像头。但ls /dev/video*结果是/dev/video0 /dev/video1 /dev/video2 /dev/video3，所以有四种不同的相机设备。
这四个摄像头冒泡到应用程序中，例如列出四个摄像头的 Skype，但只有第一个 ( /dev/video0) 有效。
有人知道其他条目来自哪里吗？或者如何从更高层隐藏它们？
我有一个 Ubuntu 18.10 并通过 snap 安装了 VSCode。
当我登录到 Wayland 会话并尝试启动 VSCode（运行vscode）时，我被注销了。
当我使用 X11 时，一切正常。
有谁知道可能是什么问题，或者可以给我一个建议如何调试这样的问题？
我正在使用带有 Gnome 的 Ubuntu 18.10。有时，整整两三天，Gnome 在从空闲屏幕保护程序恢复或挂起后崩溃。我必须手动按“Strg + Alt + F1”并再次登录才能继续，因为我只看到一个紫色屏幕。的最后输出 journalctl -b /usr/bin/gnome-shell是
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a0fb60' has no handler with id '215849'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a0fb60' has no handler with id '215850'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a73350' has no handler with id '215851'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a73350' has no handler with id '215852'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a72b90' has no handler with id '215853'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a72b90' has no handler with id '215854'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b44440' has no handler with id '215855'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b44440' has no handler with id '215856'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287b340' has no handler with id '215857'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287b340' has no handler with id '215858'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a723d0' has no handler with id '215861'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a723d0' has no handler with id '215862'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287a3c0' has no handler with id '215863'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287a3c0' has no handler with id '215864'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287ab80' has no handler with id '215865'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287ab80' has no handler with id '215866'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287bb00' has no handler with id '215867'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287bb00' has no handler with id '215868'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b44c00' has no handler with id '215869'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b44c00' has no handler with id '215870'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b453c0' has no handler with id '215871'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b453c0' has no handler with id '215872'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e1929af3f0' has no handler with id '215875'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e1929af3f0' has no handler with id '215876'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e1929afbb0' has no handler with id '215877'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e1929afbb0' has no handler with id '215878'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a0e420' has no handler with id '215879'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a0e420' has no handler with id '215880'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: Object Meta.WindowActor (0x55e192a0ebe0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: == Stack trace for context 0x55e19092c210 ==
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #0 7fff6ed0b640 b resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f8be5bcc040 @ 25)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #1 7fff6ed0b6e0 b /usr/share/gnome-shell/extensions/[email protected]/theming.js:416 (7f8bb2e65040 @ 20)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #2 7fff6ed0b7d0 b self-hosted:261 (7f8be5bc1dc0 @ 223)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #3 7fff6ed0b890 b /usr/share/gnome-shell/extensions/[email protected]/theming.js:415 (7f8bb2e60f70 @ 172)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #4 7fff6ed0c510 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #5 55e198282308 i /usr/share/gnome-shell/extensions/[email protected]/theming.js:424 (7f8bb2e650d0 @ 17)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #6 7fff6ed0d480 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #7 55e198282288 i /usr/share/gnome-shell/extensions/[email protected]/theming.js:89 (7f8bb2e60790 @ 42)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #8 7fff6ed0e3f0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #9 55e198282200 i /usr/share/gnome-shell/extensions/[email protected]/docking.js:456 (7f8bb2e565e0 @ 82)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #10 7fff6ed0f360 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #11 55e198282168 i /usr/share/gnome-shell/extensions/[email protected]/docking.js:1784 (7f8bb2e5c9d0 @ 116)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #12 7fff6ed102d0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #13 55e1982820e8 i /usr/share/gnome-shell/extensions/[email protected]/docking.js:1903 (7f8bb2e5cdc0 @ 37)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #14 7fff6ed11240 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #15 55e198282068 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:31 (7f8bb2e4ad30 @ 12)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #16 55e198281fa8 i resource:///org/gnome/shell/ui/extensionSystem.js:83 (7f8be585a040 @ 436)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #17 55e198281f28 i resource:///org/gnome/shell/ui/extensionSystem.js:354 (7f8be585ab80 @ 13)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #18 7fff6ed123b0 b self-hosted:261 (7f8be5bc1dc0 @ 223)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #19 55e198281ea8 i resource:///org/gnome/shell/ui/extensionSystem.js:353 (7f8be585aaf0 @ 64)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #20 55e198281e28 i resource:///org/gnome/shell/ui/extensionSystem.js:371 (7f8be585ac10 @ 87)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #21 7fff6ed134f0 b resource:///org/gnome/gjs/modules/signals.js:128 (7f8be5bc18b0 @ 386)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #22 7fff6ed14340 b resource:///org/gnome/shell/ui/sessionMode.js:208 (7f8be5541ca0 @ 254)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #23 7fff6ed14fc0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #24 55e198281c10 i resource:///org/gnome/shell/ui/sessionMode.js:177 (7f8be5541af0 @ 100)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #25 7fff6ed15f40 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #26 55e198281b68 i resource:///org/gnome/shell/ui/screenShield.js:1210 (7f8be55288b0 @ 105)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #27 55e198281ac0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #28 55e198281a40 i resource:///org/gnome/shell/ui/screenShield.js:1200 (7f8be5528790 @ 73)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #29 55e198281998 i resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #30 55e198281908 i resource:///org/gnome/shell/ui/screenShield.js:627 (7f8be5527040 @ 83)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #31 55e198281860 i resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #32 55e1982817a8 i resource:///org/gnome/shell/ui/screenShield.js:687 (7f8be55271f0 @ 415)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #33 55e198281700 i resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #34 55e198281640 i self-hosted:979 (7f8be5bf01f0 @ 440)
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: g_dir_open_with_errno: assertion 'path != NULL' failed
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: g_dir_open_with_errno: assertion 'path != NULL' failed
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1564]: reference to undefined property "MetaWindowXwayland"
Nov 10 17:06:12 XPS-9370 gnome-shell[7295]: Connection to xwayland lost
有人可以帮忙吗？
编辑1：我想我看到连接/断开外接显示器的连接。至少，这似乎使问题更频繁地出现。
编辑2：
sudo blkid返回
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/nvme0n1: PTUUID="4ac6dcee-933c-449a-983f-b0ede0f24c5d" PTTYPE="gpt"
/dev/nvme0n1p1: SEC_TYPE="msdos" UUID="15E7-DD98" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="1d435577-b51a-4491-b78e-b33b18783cfc"
/dev/nvme0n1p2: LABEL="OS" UUID="15F8-5108" TYPE="vfat" PARTLABEL="fat32" PARTUUID="266e101c-75bc-4d67-82b4-33dfda5d4cf6"
/dev/nvme0n1p3: UUID="7ea246ac-cdde-4c3f-acc0-40ab63d8dd47" TYPE="ext4" PARTUUID="4bd55ae7-f76f-4c8e-a8fd-3dd795e29eef"
/dev/nvme0n1p4: UUID="71013368-e9f9-4063-b176-fd9d4a73e524" TYPE="swap" PARTUUID="bf879d7d-66cf-419d-99a6-e09b192cd5eb"
/dev/nvme0n1p5: UUID="aef0d414-56c5-44ba-9dd2-55935e35b816" TYPE="ext4" PARTUUID="e9b8805d-c543-4abd-935d-2a5cff34968c"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
cat /etc/fstab返回
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=7ea246ac-cdde-4c3f-acc0-40ab63d8dd47 / ext4 errors=remount-ro 0 1
UUID=15E7-DD98 /boot/efi vfat umask=0077 0 1
UUID=71013368-e9f9-4063-b176-fd9d4a73e524 none swap sw 0 #0
UUID=aef0d414-56c5-44ba-9dd2-55935e35b816 /home ext4 defaults 0 2
cat /etc/initramfs-tools/conf.d/resume返回
RESUME=UUID=71013368-e9f9-4063-b176-fd9d4a73e524
并free -h返回
total used free shared buff/cache available
Mem: 15Gi 6,3Gi 4,3Gi 1,1Gi 4,7Gi 7,6Gi
Swap: 31Gi 11Mi 31Gi
可能没有人能给我一个明确的答案，但是如果我们将来在 Ubuntu 18.10 的官方存储库中看到 qt5-default 5.11.2，有人会吗？
在 Ubuntu 18.04 和 18.10（都带有 gnome）上，Thunderbird 不会在其基座上的符号上显示未读计数器。这正常吗？如果没有，有人知道问题可能是什么吗？
我想每周进行一次 git 提交，因此我想使用 anacron。
所以我将以下行添加到我的 /etc/anacrontab
7 1 AGDienste.weekly /bin/sh /home/bjoern/Hockey/cronWeeklyAGDiensteGitCommit.sh
cronWeeklyAGDiensteGitCommit.sh 的内容是
#!/bin/sh
cd /home/bjoern/Hockey/AGDienste
git add .
git commit --allow-empty -m "Weekly duties update `date +'%Y-%m-%d %H:%M'`"
git push
手动运行这个脚本绝对没问题。但是尝试使用sudo anacron -f以下行中的结果执行 anacron/var/log/syslog
Sep 20 23:13:52 XPS-9370 anacron[7087]: Will run job `AGDienste.weekly' in 1 min.
Sep 20 23:13:52 XPS-9370 anacron[7087]: Will run job `cron.daily' in 5 min.
Sep 20 23:13:52 XPS-9370 anacron[7087]: Will run job `cron.weekly' in 10 min.
Sep 20 23:14:52 XPS-9370 anacron[7087]: Job `AGDienste.weekly' started
Sep 20 23:14:53 XPS-9370 anacron[7087]: Job `AGDienste.weekly' terminated (exit status: 128) (mailing output)
Sep 20 23:14:53 XPS-9370 anacron[7087]: Can't find sendmail at /usr/sbin/sendmail, not mailing output
有人可以帮忙吗？
使用电池或交流电时，是否可以使用 Gnome 在 Ubuntu 18.04 中设置不同的黑屏超时？电源设置菜单仅提供一个始终应用的字段，无论当前模式如何。
不久前已经针对 Unity 桌面提出了这个问题（How can I set a different screen timeout time when on battery than if I plug in?）他们没有找到解决方案，但我希望这可能会改变现在使用 Gnome。
我有一个带有 i7-8550u CPU 的 Dell XPS 13 9370，它应该可以毫无问题地处理 Gnome。Ubuntu 版本是 18.04。但是现在遇到以下问题：当将缩放调节器设置为 powersave 时，活动概览动画非常滞后（您只能通过按 Super 键访问）。此外，我的系统以 800 MHz 的 CPU 频率闲置，但 CPU 规格显示基本频率为 1.8 GHz，这对我来说有点奇怪。如果我将调速器设置为执行这些动画绝对流畅。问题是 CPU 现在闲置在 3 GHz 左右，这会导致高电池消耗。
那么我的问题到底是什么：Gnome 动画滞后是否正常？如果是这样，我们可以期待即将发布的版本有所改进吗？intel_pstate 驱动的配置是否正确？为什么 CPU 不能足够快地提高频率以使此动画流畅？我可以禁用这个特定的动画吗？我的 CPU 以低于其描述的频率空闲是否正常？
此致
/etc/init.d/cpufrequtils 有以下注释
and which limits to set. Both MIN_SPEED and MAX_SPEED must be values
listed in:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
a value of 0 for any of the two variables will disabling the use of
that limit variable.
但是文件 /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 对我来说不存在吗？你有吗？我在哪里可以获得合适的频率？
此致