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
    • 最新
    • 标签
主页 / unix / 问题

问题[wayland](unix)

Martin Hope
Jean
Asked: 2024-07-06 16:03:01 +0800 CST

在 wayland 下调试 xkb 布局

  • 5

我有一个使用 xkb 制作的自定义布局,是我在使用 X11 时制作的。它移植到 Wayland 时效果很好。

现在我正在尝试改进布局。在 X11 下测试我的布局是使用 的问题xkbcomp mylayout.xkb $DISPLAY。当然,在 Wayland 下,这只会影响 XWayland,这意味着不会影响我的大部分桌面,这使得测试布局变得非常困难。

当然,我可以安装新版本的布局并注销并再次登录,但进行迭代和测试这是极不切实际的。

我如何才能立即在 Wayland 下应用我的布局,以便迭代和测试我的更改?我的谷歌搜索一无所获。如果这有区别的话,我会使用 KDE。

wayland
  • 1 个回答
  • 14 Views
Martin Hope
peterh
Asked: 2024-04-21 08:30:49 +0800 CST

如何从命令行启动最小的 Wayland 会话?

  • 5

调试 X 的一种方法是启动一个 X 服务器 ( X -ac :0),然后在其上启动一个 xterm ( DISPLAY=:0 xterm) 和一个 WM ( DISPLAY=:0 icewm)。

当出现显示问题时,它的用处是难以想象的。

我可以用 Wayland 做什么?我绝对不想要一个完整的 gnome,我只想要一个终端和一个虚拟机 - 并从错误输出中查看是否有任何问题。

如果可能的话,我也会想念 dbus。

wayland
  • 1 个回答
  • 33 Views
Martin Hope
71GA
Asked: 2024-03-19 06:22:53 +0800 CST

在 Sway 上使用 OBS studio 和 Pipewire

  • 6

我使用的是基于 WLR 的 Debian 12 / SWAY 桌面。


我首先安装“OBS Studio”版本29.0:

┌───┐
│ $ │ ziga > ziga--workstation > ~ 
└─┬─┘ /dev/pts/4
  └─> sudo apt install obs-studio

现在可以使用终端命令启动“OBS Studio” :

┌───┐
│ $ │ ziga > ziga--workstation > ~ 
└─┬─┘ /dev/pts/4
  └─> obs

如果“OBS Studio”默认配置为在“Xorg”上运行,我们将看不到我们的显示!如果是这种情况,我们仍然可以强制它在“Wayland”上运行,如下所示:

┌───┐
│ $ │ ziga > ziga--workstation > ~ 
└─┬─┘ /dev/pts/4
  └─> env QT_QPA_PLATFORM=wayland obs

现在它肯定使用“Wayland”,但这仍然不足以让它检测桌面!我尝试安装包:

┌───┐
│ $ │ ziga > ziga--workstation > ~ 
└─┬─┘ /dev/pts/0
  └─> sudo apt install xdg-desktop-portal xdg-desktop-portal-wlr

注意: “Sway”基于“WLR” xdg-desktop-portal-wlr ,因此我们为xdg-desktop-portal. 存在不同的“门户”实现,并且应该为不同的桌面安装。Debian 支持“ KDE” ( )、“GTK” ( ) 或“Gnome” ( ) 的“门户”。xdg-desktop-portal-kdexdg-desktop-portal-gtkxdg-desktop-portal-gnome

我测试并得出结论,使用哪个“Pipewire 会话管理器”并不重要。默认情况下,人们使用pipewire-media-session但我使用wireplumber它不推荐使用pipewire-media-session(链接)。

此时我在“OBS Studio”中没有显示任何屏幕!但我可以使用简单的 CLI 录像机来录制我的屏幕和麦克风,如下所示:

┌───┐
│ $ │ ziga > ziga--workstation > ~ 
└─┬─┘ /dev/pts/0
  └─> sudo apt install wl-recorder
┌───┐
│ $ │ ziga > ziga--workstation > ~ 
└─┬─┘ /dev/pts/0
  └─> pw-jack wf-recorder -a

这就像一个魅力......

只是“OBS Studio”无法工作......

wayland
  • 1 个回答
  • 51 Views
Martin Hope
Jan Černý
Asked: 2023-12-16 02:42:43 +0800 CST

Arch linux:AMD ryzen + AMD radeon 遇到浏览器冻结和崩溃问题

  • 7

我通过更换 SSD 将安装从 intel i7 + intel iris 转移到 AMD ryzen 5 + AMD radeon。我遇到这些问题:


症状

  • 一切工作正常,除了 CPU 负载随机爆炸到 30+ 并且系统冻结了几分钟。
  • 所有 Firefox、Brave 和 Electron 应用程序都会随机崩溃。我高度怀疑这将是具有硬件加速功能的东西。
  • 启动时我AMDGPU securedisplay: generic failrure在日志中看到这是在journalctl中:
Dec 18 02:26:00 archlinux kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
Dec 18 02:26:00 archlinux kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
  • Sway 随机崩溃
  • Discord 崩溃并显示以下消息:
[109734:1216/144012.453719:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: BGRA_8888, share_between_threads: 0, gmb_type: shared_memory
[109734:1216/144018.594445:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: BGRA_8888, share_between_threads: 0, gmb_type: shared_memory
[109734:1216/144025.341187:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: BGRA_8888, share_between_threads: 0, gmb_type: shared_memory
[109688:1216/144035.692207:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=9
(electron) 'gpu-process-crashed event' is deprecated and will be removed. Please use 'child-process-gone event' instead.
notificationScreen.webContentsSend: win is invalid undefined.
child-process-gone! child: GPU (undefined) exitCode: 9
blackbox: 2023-12-16T13:40:35.738Z 59 before-quit
blackbox: 2023-12-16T13:40:35.763Z 60 window.close win8
blackbox: 2023-12-16T13:40:35.772Z 61 ❌ child-process-gone { type: 'GPU', reason: 'killed', exitCode: 9, serviceName: 'GPU' }
blackbox: 2023-12-16T13:40:36.319Z 62 webContents.destroyed web8
  • 这是 Brave 浏览器日志:
[158080:158080:1218/173945.959830:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[158080:158080:1218/173945.966721:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[158080:158080:1218/173950.934755:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
Warning: terminator_CreateInstance: Failed to CreateInstance in ICD 0.  Skipping ICD.
Warning: terminator_CreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:101)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:493)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:379)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:301)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:556)
  • 经过一次强烈的冻结后,我在以下位置发现了这一点journalctl:
Dec 23 22:19:05 arch-thinkpad kernel: Out of memory: Killed process 2068 (electron) total-vm:1190296860kB, anon-rss:175928kB, file-rss:256kB, shmem-rss:600kB, UID:1000 pgtables:1752kB oom_score_adj:300
Dec 23 22:21:22 arch-thinkpad kernel: Out of memory: Killed process 10923 (brave) total-vm:1186204220kB, anon-rss:51484kB, file-rss:512kB, shmem-rss:3648kB, UID:1000 pgtables:928kB oom_score_adj:300
Dec 23 22:21:33 arch-thinkpad kernel: Out of memory: Killed process 8797 (brave) total-vm:1186202212kB, anon-rss:51528kB, file-rss:256kB, shmem-rss:1084kB, UID:1000 pgtables:1008kB oom_score_adj:300
Dec 23 22:21:34 arch-thinkpad kernel: Out of memory: Killed process 8753 (brave) total-vm:1186222336kB, anon-rss:50016kB, file-rss:384kB, shmem-rss:1252kB, UID:1000 pgtables:1016kB oom_score_adj:300
  • Firefox 经常崩溃并显示以下日志:
[Parent 2974, IPC I/O Parent] WARNING: process 3081 exited on signal 11: file /build/firefox/src/firefox-121.0/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 2974, IPC I/O Parent] WARNING: process 3917 exited on signal 11: file /build/firefox/src/firefox-121.0/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 2974, IPC I/O Parent] WARNING: process 3958 exited on signal 11: file /build/firefox/src/firefox-121.0/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 2974, IPC I/O Parent] WARNING: process 3633 exited on signal 11: file /build/firefox/src/firefox-121.0/ipc/chromium/src/base/process_util_posix.cc:265
ExceptionHandler::GenerateDump cloned child 7802
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Failed to open curl lib from binary, use libcurl.so instead
ExceptionHandler::GenerateDump cloned child 10410
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Failed to open curl lib from binary, use libcurl.so instead

Chromium 浏览器在启动时立即崩溃:

[32424:32424:0109/161137.203058:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build.
[32500:1:0109/161137.867689:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[32424:32424:0109/161137.868183:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=139
[32500:1:0109/161138.480418:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[32573:1:0109/161138.480549:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[32583:1:0109/161138.481906:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[32424:32452:0109/161138.483240:ERROR:shared_image_interface_proxy.cc(136)] Buffer handle is null. Not creating a mailbox from it.
[32424:32452:0109/161138.483260:ERROR:one_copy_raster_buffer_provider.cc(365)] Creation of MappableSharedImage failed.
[32424:32452:0109/161138.483313:ERROR:shared_image_interface_proxy.cc(136)] Buffer handle is null. Not creating a mailbox from it.
[32424:32424:0109/161138.484013:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=139
[32543:1:0109/161139.231084:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[32573:1:0109/161139.231223:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[32424:32452:0109/161139.232795:ERROR:shared_image_interface_proxy.cc(136)] Buffer handle is null. Not creating a mailbox from it.
[32424:32452:0109/161139.232810:ERROR:one_copy_raster_buffer_provider.cc(365)] Creation of MappableSharedImage failed.
[32424:32424:0109/161139.232827:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=139
[32714:32714:0109/161139.240747:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
[32714:32714:0109/161139.240832:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
[32714:32714:0109/161139.240859:ERROR:gl_display.cc(786)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[32714:32714:0109/161139.240894:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
[32714:32714:0109/161139.240917:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[32714:32714:0109/161139.241169:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
[32714:32714:0109/161139.241204:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
[32714:32714:0109/161139.241228:ERROR:gl_display.cc(786)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[32714:32714:0109/161139.241250:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
[32714:32714:0109/161139.241277:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[32714:32714:0109/161139.242947:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[32424:32424:0109/161139.654097:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=139
[32424:32424:0109/161140.509961:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
fish: Job 1, 'chromium 2> chromium-log' terminated by signal SIGTRAP (Trace or breakpoint trap)

更多信息

眼镜:

  • 我使用带有 arch linux + wayland + sway 的 HP 笔记本电脑
  • CPU:AMD Ryzen 5 4500U,带 Radeon 显卡 (6) @ 2.375GHz
  • GPU:AMD ATI Radeon RX Vega 6
  • 我有 8Gb 或 RAM,~~没有交换~~,SSD 上有 8GB 交换文件

这是已安装软件包的列表,其中包含amd:

local/amd-ucode 20231211.f2e52a1c-1
    Microcode update image for AMD CPUs
local/amf-headers 1.4.32-1
    Header files for AMD Advanced Media Framework
local/libteam 1.32-1
    Library for controlling team network device
local/nvtop 3.0.2-1
    GPUs process monitoring for AMD, Intel and NVIDIA
local/rocm-dbgapi 5.7.1-1
    Support library necessary for a debugger of AMD's GPUs

这是包含以下内容的软件包列表radeon:

local/hsakmt-roct 5.7.1-1
    Radeon Open Compute Thunk Interface
local/lib32-vulkan-radeon 1:23.3.1-1
    Radeon's Vulkan mesa driver (32-bit)
local/vulkan-radeon 1:23.3.1-1
    Radeon's Vulkan mesa driver

这是输出lspci -nn:

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51)
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0 [1022:1448]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1 [1022:1449]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2 [1022:144a]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3 [1022:144b]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4 [1022:144c]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5 [1022:144d]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6 [1022:144e]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7 [1022:144f]
01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter [10ec:c822]
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01)
03:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO [144d:a80a]
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)] [1002:1636] (rev c3)
04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
04:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
04:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
04:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 01)
04:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3]
04:00.7 Signal processing controller [1180]: Advanced Micro Devices, Inc. [AMD] Sensor Fusion Hub [1022:15e4]

输出lspci -k | grep -A 3 -E "(VGA|3D)":

04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)] (rev c3)
    DeviceName: AMD Radeon(TM) Graphics
    Subsystem: Hewlett-Packard Company Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)]
    Kernel driver in use: amdgpu

我在日志中发现了这一点dmesg:

[    2.906817] [drm] amdgpu kernel modesetting enabled.
[    2.907464] amdgpu: Virtual CRAT table created for CPU
[    2.907479] amdgpu: Topology: Add CPU node
[    2.907685] amdgpu 0000:04:00.0: enabling device (0006 -> 0007)
[    2.907739] [drm] initializing kernel modesetting (RENOIR 0x1002:0x1636 0x103C:0x876E 0xC3).
[    2.934103] [drm] register mmio base: 0xD0400000
[    2.934114] [drm] register mmio size: 524288
[    2.937640] [drm] add ip block number 0 <soc15_common>
[    2.937644] [drm] add ip block number 1 <gmc_v9_0>
[    2.937646] [drm] add ip block number 2 <vega10_ih>
[    2.937647] [drm] add ip block number 3 <psp>
[    2.937649] [drm] add ip block number 4 <smu>
[    2.937651] [drm] add ip block number 5 <dm>
[    2.937652] [drm] add ip block number 6 <gfx_v9_0>
[    2.937654] [drm] add ip block number 7 <sdma_v4_0>
[    2.937655] [drm] add ip block number 8 <vcn_v2_0>
[    2.937656] [drm] add ip block number 9 <jpeg_v2_0>
[    2.937681] amdgpu 0000:04:00.0: amdgpu: Fetched VBIOS from VFCT
[    2.937684] amdgpu: ATOM BIOS: 113-RENOIR-026
[    2.939454] [drm] VCN decode is enabled in VM mode
[    2.939456] [drm] VCN encode is enabled in VM mode
[    2.940642] [drm] JPEG decode is enabled in VM mode
[    2.954319] Console: switching to colour dummy device 80x25
[    2.988195] amdgpu 0000:04:00.0: vgaarb: deactivate vga console
[    2.988210] amdgpu 0000:04:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
[    2.988218] amdgpu 0000:04:00.0: amdgpu: MODE2 reset
[    2.988323] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[    2.988337] amdgpu 0000:04:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
[    2.988342] amdgpu 0000:04:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
[    2.988345] amdgpu 0000:04:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
[    2.988357] [drm] Detected VRAM RAM=512M, BAR=512M
[    2.988360] [drm] RAM width 128bits DDR4
[    2.988686] [drm] amdgpu: 512M of VRAM memory ready
[    2.988692] [drm] amdgpu: 3661M of GTT memory ready.
[    2.988726] [drm] GART: num cpu pages 262144, num gpu pages 262144
[    2.988934] [drm] PCIE GART of 1024M enabled.
[    2.988936] [drm] PTB located at 0x000000F41FC00000
[    2.989313] [drm] Loading DMUB firmware via PSP: version=0x01010028
[    2.989963] [drm] Found VCN firmware Version ENC: 1.21 DEC: 6 VEP: 0 Revision: 0
[    2.989970] amdgpu 0000:04:00.0: amdgpu: Will use PSP to load VCN firmware
[    3.649478] [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR
[    3.744619] amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
[    3.754153] amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
[    3.759165] [drm] psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
[    3.759289] [drm] psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
[    3.759293] amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
[    3.759305] amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
[    3.759720] amdgpu 0000:04:00.0: amdgpu: SMU is initialized successfully!
[    3.760994] [drm] Display Core v3.2.247 initialized on DCN 2.1
[    3.760998] [drm] DP-HDMI FRL PCON supported
[    3.761775] [drm] DMUB hardware initialized: version=0x01010028
[    4.104152] [drm] Alt mode has timed out after 202 ms
[    4.106330] [drm] kiq ring mec 2 pipe 1 q 0
[    4.109571] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[    4.109599] [drm] JPEG decode initialized successfully.
[    4.136633] amdgpu: HMM registered 512MB device memory
[    4.138946] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[    4.138968] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[    4.139127] amdgpu: Virtual CRAT table created for GPU
[    4.139236] amdgpu: Topology: Add dGPU node [0x1636:0x1002]
[    4.139239] kfd kfd: amdgpu: added device 1002:1636
[    4.139253] amdgpu 0000:04:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 6
[    4.139421] amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[    4.139424] amdgpu 0000:04:00.0: amdgpu: ring gfx_low uses VM inv eng 1 on hub 0
[    4.139425] amdgpu 0000:04:00.0: amdgpu: ring gfx_high uses VM inv eng 4 on hub 0
[    4.139427] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 5 on hub 0
[    4.139428] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 6 on hub 0
[    4.139430] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 7 on hub 0
[    4.139431] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 8 on hub 0
[    4.139432] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 9 on hub 0
[    4.139434] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 10 on hub 0
[    4.139435] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 11 on hub 0
[    4.139437] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 12 on hub 0
[    4.139438] amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 13 on hub 0
[    4.139439] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
[    4.139441] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
[    4.139443] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
[    4.139444] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
[    4.139445] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
[    4.141078] [drm] Initialized amdgpu 3.54.0 20150101 for 0000:04:00.0 on minor 1
[    4.147509] fbcon: amdgpudrmfb (fb0) is primary device
[    4.147823] [drm] DSC precompute is not needed.
[    4.854418] Console: switching to colour frame buffer device 240x67
[    4.874494] amdgpu 0000:04:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[   11.871434] Key type trusted registered
[   11.886779] Key type encrypted registered

...

[ 3001.667474] ThreadPoolForeg[7212]: segfault at 3fe173700008 ip 00005632b4aca97b sp 00007f667e7efdc0 error 4 in electron[5632b332f000+7732000] likely on CPU 0 (core 0, socket 0)
[ 3001.667500] Code: 06 48 03 08 5d e9 25 0c 00 00 cc cc cc cc cc 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 49 89 cd 49 81 e5 00 00 fc ff <41> f6 45 08 40 0f 85 a1 00 00 00 49 89 cf 49 89 f6 80 7f 3a 00 75
[ 4538.486544] electron[8432]: segfault at 80000000008 ip 00005578c8450e12 sp 00007fff90612410 error 4 in electron[5578c26d9000+7aaf000] likely on CPU 4 (core 5, socket 0)
[ 4538.486557] Code: f0 0f b1 0f 75 f2 eb 06 67 e8 7a 7d dc fe 48 8b bb b0 01 00 00 48 85 ff 0f 85 8e 01 00 00 48 8b bb a8 01 00 00 48 85 ff 74 24 <8b> 47 08 a8 02 75 1d 8b 07 0f 1f 44 00 00 83 f8 01 74 0b 8d 48 ff
[ 4595.501146] Isolated Web Co[10781]: segfault at 7702dd668c80 ip 00007f02e972e336 sp 00007ffc2f669840 error 4 in libxul.so[7f02e8f3a000+5f91000] likely on CPU 4 (core 5, socket 0)
[ 4595.501158] Code: 24 20 48 8b b4 24 a0 00 00 00 48 85 f6 0f 84 2c 01 00 00 8b 84 24 a8 00 00 00 48 3d ff ff ff 7f 0f 83 4e 0b 00 00 48 8b 4d 00 <8b> 11 0f ba e2 1e 0f 83 67 01 00 00 8b 79 08 48 29 f9 4c 89 4c 24

这是输出eglinfo -B:

GBM platform:
eglinfo: eglInitialize failed

Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

这些是我的内核参数:

Kernel command line: initrd=\amd-ucode.img initrd=\initramfs-linux.img root="LABEL=arch_os" rw i915.enable_psr=0 rd.luks.name=02e...eee=root CONFIG_DRM_AMDGPU_CIK=Y

我尝试过的:

  • 我安装了 AMD 微码并在 systemdboot 的加载器选项中进行了设置
  • 我将内核更新到最新的
  • 我安装了xf86-video-amdgpu
  • 我使用更新了所有固件fwupdmgr
  • 我卸载了 X.org 驱动程序 ( xf86-video-amdgpu)
  • 我卸载了所有amdvlk驱动程序并安装了 radeon 驱动程序
  • 我安装了桌面门户
  • 我添加CONFIG_DRM_AMDGPU_CIK=Y到内核参数。这会产生Unknown kernel command line parameters "CONFIG_DRM_AMDGPU_CIK=Y", will be passed to user space.dmesg。
  • 我尝试添加radeon.dpm=0但radeon.dpm=1没有效果
  • 我尝试记录 sway 的调试日志,但没有发现任何有趣的东西
  • 我删除了~/.cache/mesa目录
  • 添加 8GB 交换对冻结有一点帮助,但不能解决崩溃问题。程序崩溃得更快。

似乎没有什么可以解决这个问题。


问题

我应该怎么做才能摆脱这种冻结和崩溃?您对如何诊断此类问题有什么建议吗?
谢谢你的帮助

wayland
  • 1 个回答
  • 480 Views
Martin Hope
charmoniumQ
Asked: 2023-08-05 03:08:53 +0800 CST

如何在 Python/Wayland/Linux 中编写使用多个鼠标作为不同输入的应用程序?

  • 6

我想编写一个模拟危险蜂鸣器的应用程序。一台主机连接 N 个鼠标,充当每个玩家的蜂鸣器。

用 Python 编写此应用程序的最简单方法是什么?理想的解决方案将避免篡改或创建新的物理硬件。

我正在考虑的选项:

  • 我听说 USB 设备被操作系统以纯文本流的形式读取。但是哪里?
  • 我还可以将每个按钮绑定到不同的键,然后只监听键盘事件。是否可以将 mouse-0 的右键单击绑定到 key-0,而将 mouse-1 的右键单击绑定到 key-1?或者所有右键单击都绑定到同一个键吗?

有很多选择,我想知道什么是最简单的?另外,我所做的很多阅读都是针对 X11(xinput this或xev that)的。在 Wayland 中应该如何做同样的事情?

wayland
  • 1 个回答
  • 23 Views
Martin Hope
nimbin
Asked: 2023-02-25 21:25:37 +0800 CST

在 Wayland 摇摆下校准外接显示器的触摸屏

  • 5

如何在 wayland - sway 下校准外接显示器的触摸屏?

如果我插入一个支持触摸的外接显示器,触摸输入将映射到主显示器,而不是外接显示器。

wayland
  • 1 个回答
  • 15 Views
Martin Hope
Marcus Müller
Asked: 2022-05-19 00:50:30 +0800 CST

容器:无法开始喃喃自语(作为带有 gnome 会话的无头 Wayland 合成器)

  • 2

我想做的是拥有

  • 一个容器(最好是 OCI 容器),它可以在没有主机会话管理器接口“暴露”它的情况下工作,并且
  • 运行一个 Wayland 合成器
  • 有一个 >= gnome40 会话,包括其中的所有 UI 元素
  • 允许通过 RDP 或 VNC 进行远程显示和交互

因此,这分别指示/建议作为工具:

  • podman
  • mutter(正如 Gnome 想要的那样)
  • gnome-shell
  • gnome-remote-desktop, Gnome42 自带的

我目前正在做的是

podman run -it --rm -p 9999:9999 ubuntu:22.04
#           ^---------------------------------Interactive
#               ^-----------------------------Don't keep state after finishing
#                    ^------------------------We'll need a port fwd into the container for RDP/VNC
#                                ^------------Not a great fan of Canonical, but 22.04 brings Gnome42

root@container$> apt update; apt install -y mutter gnome-remote-desktop gnome-shell
[… [success]]

root@container$> mutter --no-x11 --wayland --headless --virtual-monitor 1600x1000 
mutter-Message: 10:30:35.151: Running Mutter (using mutter 42.0) as a Wayland display server
mutter-Message: 10:30:35.191: Created surfaceless renderer without GPU
mutter-Message: 10:30:35.205: Disabling DMA buffer screen sharing (not hardware accelerated)
mutter-Message: 10:30:35.205: Added virtual monitor Meta-0

(mutter:13413): mutter-WARNING **: 10:30:35.211: WL: error: XDG_RUNTIME_DIR not set in the environment
(mutter:13413): mutter-ERROR **: 10:30:35.211: Failed to create socket
root@container$> export XDG_RUNTIME_DIR=/run/user/0/ ; mkdir -p ${XDG_RUNTIME_DIR}
root@container$> mutter --no-x11 --wayland --headless --virtual-monitor 1600x1000 
mutter-Message: 10:30:47.657: Running Mutter (using mutter 42.0) as a Wayland display server
mutter-Message: 10:30:47.698: Created surfaceless renderer without GPU
mutter-Message: 10:30:47.712: Disabling DMA buffer screen sharing (not hardware accelerated)
mutter-Message: 10:30:47.712: Added virtual monitor Meta-0
mutter-Message: 10:30:47.717: Using Wayland display name 'wayland-0'
**
mutter:ERROR:../src/wayland/meta-wayland.c:379:set_gnome_env: assertion failed: (session_bus)
Bail out! mutter:ERROR:../src/wayland/meta-wayland.c:379:set_gnome_env: assertion failed: (session_bus)

[1]+  Aborted                 (core dumped) mutter --sm-disable --no-x11 --wayland --headless --virtual-monitor 1600x1000

不太确定从这里去哪里。我应该直接启动一个 gnome shell 吗?

# fresh container to avoid any conflicts
root@7396d1bb8693:/> gnome-shell --no-x11 --wayland --headless --virtual-monitor 1600x1000
mutter-Message: 10:45:06.276: Running GNOME Shell (using mutter 42.0) as a Wayland display server
mutter-Message: 10:45:06.323: Created surfaceless renderer without GPU
mutter-Message: 10:45:06.337: Disabling DMA buffer screen sharing (not hardware accelerated)
mutter-Message: 10:45:06.338: Added virtual monitor Meta-0
Failed to connect to session bus: Cannot autolaunch D-Bus without X11 $DISPLAYroot@7396d1bb8693:/>

也不行。

  • 如何在非特权容器中启动无头 gnome wayland 会话?
gnome wayland
  • 1 个回答
  • 423 Views
Martin Hope
karthik nair
Asked: 2021-12-08 04:35:54 +0800 CST

有人可以解释一下这个名为@!0,35 的不可点击的永久窗口是什么;BDHF 总是在 Wayland 上打开?

  • 4

Pop!_OS 21.10、amdgpu、ryzen 5 4500u,仅在 Wayland 上发行。
Linux 5.15.5-76051505-通用

附在在此处输入图像描述下面的快照(我什至无法截图那个东西)。

gnome wayland
  • 1 个回答
  • 276 Views
Martin Hope
piegames
Asked: 2020-02-24 11:11:37 +0800 CST

在 Wayland 上禁用笔记本电脑触摸板

  • 4

我需要禁用笔记本电脑的触摸板。我在 Wayland 上使用 Gnome 。

  • libinput应该提供这个功能,但显然它没有。
  • xinput不起作用,因为我在 Wayland。
  • 我认为 Gnome 在输入设置中提供了一些开关,但它不再存在(Gnome shell 3.34 — 也许这是 Xorg 独有的功能?)。

如果我想禁用输入设备,是否真的问得太多了?


编辑:xinput不是解决方案!

它的手册页有一整节关于 Wayland(强调我的):

XWAYLAND

Xwayland 是一个使用 Wayland 合成器作为后端的 X 服务器。Xwayland 充当 X 协议和 Wayland 协议之间的转换层,但不能直接访问硬件。Xwayland 创建的 X 输入扩展设备(“xwayland-pointer”、“xwayland-keyboard”等)映射到 Wayland 协议设备,而不是物理设备。这些 X 输入扩展设备仅对连接到同一 Xwayland 进程的其他 X 客户端可见。更改 Xwayland 设备上的属性只会影响这些客户端的行为。例如,使用 xinput 禁用 Xwayland 设备不会禁用 Wayland 原生应用程序中的设备. 其他更改可能根本没有任何影响。在大多数情况下,将 xinput 与 Xwayland 设备一起使用表示 shell 脚本中存在错误,并且 xinput 将打印警告。请改用 Wayland 合成器的本机设备配置方法。

TL;DR:如果我使用 禁用触摸板xinput,它仍会像以前一样继续工作,但 XWayland 应用程序将不再看到光标移动。

wayland touchpad
  • 2 个回答
  • 5056 Views
Martin Hope
AlphaShadows
Asked: 2019-08-13 05:31:07 +0800 CST

在 Sway 上启动 gnome-terminal 时出错

  • 0

我已经安装了 gnome-terminal 和 xorg-server-xwayland,现在我正在尝试启动 gnome-terminal。

我已经遇到了由高于 255 的键码引起的错误。我删除了高于 255 的键码,问题得到解决,但我还有另一个问题:

[...]
glamor: No eglstream capable devices found
[...]

# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0 : Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached"

任何人都有解决这个问题的想法?

可能有用的信息:

  • 操作系统:ArchLinux
  • 内核版本:5.2.8-arch1-1-ARCH
  • X服务器:韦兰
  • 作曲:摇摆
wayland gnome-terminal
  • 1 个回答
  • 840 Views

Sidebar

Stats

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

    模块 i915 可能缺少固件 /lib/firmware/i915/*

    • 3 个回答
  • Marko Smith

    无法获取 jessie backports 存储库

    • 4 个回答
  • Marko Smith

    如何将 GPG 私钥和公钥导出到文件

    • 4 个回答
  • Marko Smith

    我们如何运行存储在变量中的命令?

    • 5 个回答
  • Marko Smith

    如何配置 systemd-resolved 和 systemd-networkd 以使用本地 DNS 服务器来解析本地域和远程 DNS 服务器来解析远程域?

    • 3 个回答
  • Marko Smith

    dist-upgrade 后 Kali Linux 中的 apt-get update 错误 [重复]

    • 2 个回答
  • Marko Smith

    如何从 systemctl 服务日志中查看最新的 x 行

    • 5 个回答
  • Marko Smith

    Nano - 跳转到文件末尾

    • 8 个回答
  • Marko Smith

    grub 错误:你需要先加载内核

    • 4 个回答
  • Marko Smith

    如何下载软件包而不是使用 apt-get 命令安装它?

    • 7 个回答
  • Martin Hope
    user12345 无法获取 jessie backports 存储库 2019-03-27 04:39:28 +0800 CST
  • Martin Hope
    Carl 为什么大多数 systemd 示例都包含 WantedBy=multi-user.target? 2019-03-15 11:49:25 +0800 CST
  • Martin Hope
    rocky 如何将 GPG 私钥和公钥导出到文件 2018-11-16 05:36:15 +0800 CST
  • Martin Hope
    Evan Carroll systemctl 状态显示:“状态:降级” 2018-06-03 18:48:17 +0800 CST
  • Martin Hope
    Tim 我们如何运行存储在变量中的命令? 2018-05-21 04:46:29 +0800 CST
  • Martin Hope
    Ankur S 为什么 /dev/null 是一个文件?为什么它的功能不作为一个简单的程序来实现? 2018-04-17 07:28:04 +0800 CST
  • Martin Hope
    user3191334 如何从 systemctl 服务日志中查看最新的 x 行 2018-02-07 00:14:16 +0800 CST
  • Martin Hope
    Marko Pacak Nano - 跳转到文件末尾 2018-02-01 01:53:03 +0800 CST
  • Martin Hope
    Kidburla 为什么真假这么大? 2018-01-26 12:14:47 +0800 CST
  • Martin Hope
    Christos Baziotis 在一个巨大的(70GB)、一行、文本文件中替换字符串 2017-12-30 06:58:33 +0800 CST

热门标签

linux bash debian shell-script text-processing ubuntu centos shell awk ssh

Explore

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

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve