Discord shows black/empty window on Manjaro (KDE, Wayland, AMD GPU)

Description

Discord starts but the window remains completely black and empty.
The application does not crash immediately, but the UI never renders.

This started before Discord 0.0.124 - at least the version before that.

System information

  • Distribution: Manjaro Linux (26.0.2, testing branch)
  • Desktop environment: KDE Plasma
  • Session: Wayland
  • GPU: AMD (RADV / Mesa)
  • Discord version: 0.0.124 (official Manjaro package)
  • Kernel: 6.19.0-1-MANJARO

Steps to reproduce

  1. Launch Discord normally:
discord
  1. Discord window opens but remains black and empty.

Observed behavior

  • Window opens but shows no UI (black screen).
  • Terminal output:
 discord                                                                                                                                                                                                                                 ✔ 
Discord 0.0.124
(electron) 'session.getPreloads' is deprecated and will be removed. Please use 'session.getPreloadScripts' instead.
(electron) 'session.setPreloads' is deprecated and will be removed. Please use 'session.registerPreloadScript' instead.
Starting app.
Starting updater.
2/10/2026, 2:02:38 PM GMT [Modules] Modules initializing
2/10/2026, 2:02:38 PM GMT [Modules] Distribution: remote
2/10/2026, 2:02:38 PM GMT [Modules] Host updates: enabled
2/10/2026, 2:02:38 PM GMT [Modules] Module updates: enabled
2/10/2026, 2:02:38 PM GMT [Modules] Module install path: /home/jorgecpd/.config/discord/0.0.124/modules
2/10/2026, 2:02:38 PM GMT [Modules] Module installed file path: /home/jorgecpd/.config/discord/0.0.124/modules/installed.json
2/10/2026, 2:02:38 PM GMT [Modules] Module download path: /home/jorgecpd/.config/discord/0.0.124/modules/pending
splashScreen.initSplash(false)
blackbox: 2/10/2026, 2:02:38 PM GMT 0 

----------------------------------------------
blackbox: 2/10/2026, 2:02:38 PM GMT 1 Discord starting: {"releaseChannel":"stable","version":"0.0.124"}, modulepath: /home/jorgecpd/.config/discord/0.0.124/modules
blackbox: 2/10/2026, 2:02:38 PM GMT 2 ✅ webContents.created web1 "index.html"
blackbox: 2/10/2026, 2:02:38 PM GMT 3 ✅ window.created win1 "discord"
(electron) 'console-message' arguments are deprecated and will be removed. Please use Event<WebContentsConsoleMessageEventParams> object instead.
14:02:38.853 › DiscordSplash.signalReady
splashScreen: SPLASH_SCREEN_READY
splashScreen.webContentsSend: SPLASH_SCREEN_QUOTE SPLASH_SCREEN_QUOTE [ 'Hold Tight — Loading Discord' ]
2/10/2026, 2:02:38 PM GMT [Modules] No updates to install
splashScreen: no-pending-updates
2/10/2026, 2:02:38 PM GMT [Modules] Checking for host updates.
splashScreen: checking-for-updates
splashScreen.updateSplashState checking-for-updates checking-for-updates {}
splashScreen.webContentsSend: SPLASH_UPDATE_STATE SPLASH_UPDATE_STATE [ { status: 'checking-for-updates' } ]
14:02:38.859 › DiscordSplash.onStateUpdate: {"status":"checking-for-updates"}
14:02:38.860 › Splash.onStateUpdate: {"status":"checking-for-updates"}
blackbox: 2/10/2026, 2:02:38 PM GMT 4 ✅ webContents.did-finish-load web1
[ConnectivityTester 68ktqa] Sending DNS query: idt-68ktqa-mlgo7id4.loc-en-gb.chk-updaterdep.res-err.err-403-status-403.dur-0.v1.dc-telemetry.net
Error downloading with electron net: https://discord.com/api/updates/stable?platform=linux&version=0.0.124 HTTP Error: Status Code 403
Falling back to node net library..
2/10/2026, 2:02:39 PM GMT [Modules] Host is up to date.
2/10/2026, 2:02:39 PM GMT [Modules] Checking for module updates at https://discord.com/api/modules/stable/versions.json
Error downloading with electron net: https://discord.com/api/modules/stable/versions.json HTTP Error: Status Code 403
Falling back to node net library..
14:02:39.852 › Splash.updateCountdownSeconds: undefined
2/10/2026, 2:02:39 PM GMT [Modules] No module updates available.
splashScreen: update-check-finished true 0 false
splashScreen.launchMainWindow: false
Optional module ./ElectronTestRpc was not included.
Clearing GPU cache...
splashScreen.updateSplashState launching launching {}
splashScreen.webContentsSend: SPLASH_UPDATE_STATE SPLASH_UPDATE_STATE [ { status: 'launching' } ]
blackbox: 2/10/2026, 2:02:39 PM GMT 5 ✅ webContents.created web2 ""
14:02:39.985 › DiscordSplash.onStateUpdate: {"status":"launching"}
14:02:39.985 › Splash.onStateUpdate: {"status":"launching"}
Clearing code cache...
blackbox: 2/10/2026, 2:02:39 PM GMT 6 ✅ window.created win2 "Discord"
[ConnectivityTester 68ktqa] Sending DNS query: idt-68ktqa-mlgo7j39.loc-en-gb.chk-webapp.res-err.err-403-status-403.dur-0.v1.dc-telemetry.net
blackbox: 2/10/2026, 2:02:40 PM GMT 7 ✅ webContents.did-finish-load web2
14:02:40.852 › Splash.updateCountdownSeconds: undefined
14:02:41.852 › Splash.updateCountdownSeconds: undefined
14:02:42.852 › Splash.updateCountdownSeconds: undefined
14:02:43.852 › Splash.updateCountdownSeconds: undefined
[85760:0210/140243.949337:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 1 times!
[...]

Disabling GPU causes Discord to fail at startup:

discord --disable-gpu --disable-software-rasterizer

Error:

Error bootstrapping: Error: GPU access not allowed.
Reason: GPU access is disabled through commandline switch

I’ve also tried :

discord --enable-features=UseOzonePlatform --ozone-platform=x11                                                                                                                                                                         ✔

The output :

Discord 0.0.124
(electron) 'session.getPreloads' is deprecated and will be removed. Please use 'session.getPreloadScripts' instead.
(electron) 'session.setPreloads' is deprecated and will be removed. Please use 'session.registerPreloadScript' instead.
Starting app.
Starting updater.
2/10/2026, 1:45:44 PM GMT [Modules] Modules initializing
2/10/2026, 1:45:44 PM GMT [Modules] Distribution: remote
2/10/2026, 1:45:44 PM GMT [Modules] Host updates: enabled
2/10/2026, 1:45:44 PM GMT [Modules] Module updates: enabled
2/10/2026, 1:45:44 PM GMT [Modules] Module install path: /home/jorgecpd/.config/discord/0.0.124/modules
2/10/2026, 1:45:44 PM GMT [Modules] Module installed file path: /home/jorgecpd/.config/discord/0.0.124/modules/installed.json
2/10/2026, 1:45:44 PM GMT [Modules] Module download path: /home/jorgecpd/.config/discord/0.0.124/modules/pending
splashScreen.initSplash(false)
blackbox: 2/10/2026, 1:45:44 PM GMT 0 

----------------------------------------------
blackbox: 2/10/2026, 1:45:44 PM GMT 1 Discord starting: {"releaseChannel":"stable","version":"0.0.124"}, modulepath: /home/jorgecpd/.config/discord/0.0.124/modules
blackbox: 2/10/2026, 1:45:44 PM GMT 2 ✅ webContents.created web1 "index.html"
blackbox: 2/10/2026, 1:45:44 PM GMT 3 ✅ window.created win1 "discord"
(electron) 'console-message' arguments are deprecated and will be removed. Please use Event<WebContentsConsoleMessageEventParams> object instead.
13:45:44.992 › DiscordSplash.signalReady
splashScreen: SPLASH_SCREEN_READY
splashScreen.webContentsSend: SPLASH_SCREEN_QUOTE SPLASH_SCREEN_QUOTE [ 'Hold Tight — Loading Discord' ]
2/10/2026, 1:45:44 PM GMT [Modules] No updates to install
splashScreen: no-pending-updates
2/10/2026, 1:45:44 PM GMT [Modules] Checking for host updates.
splashScreen: checking-for-updates
splashScreen.updateSplashState checking-for-updates checking-for-updates {}
splashScreen.webContentsSend: SPLASH_UPDATE_STATE SPLASH_UPDATE_STATE [ { status: 'checking-for-updates' } ]
13:45:45.008 › DiscordSplash.onStateUpdate: {"status":"checking-for-updates"}
13:45:45.009 › Splash.onStateUpdate: {"status":"checking-for-updates"}
blackbox: 2/10/2026, 1:45:45 PM GMT 4 ✅ webContents.did-finish-load web1
[ConnectivityTester xmr2jf] Sending DNS query: idt-xmr2jf-mlgnls2d.loc-en-gb.chk-updaterdep.res-err.err-403-status-403.dur-0.v1.dc-telemetry.net
Error downloading with electron net: https://discord.com/api/updates/stable?platform=linux&version=0.0.124 HTTP Error: Status Code 403
Falling back to node net library..
2/10/2026, 1:45:45 PM GMT [Modules] Host is up to date.
2/10/2026, 1:45:45 PM GMT [Modules] Checking for module updates at https://discord.com/api/modules/stable/versions.json
13:45:45.992 › Splash.updateCountdownSeconds: undefined
Error downloading with electron net: https://discord.com/api/modules/stable/versions.json HTTP Error: Status Code 403
Falling back to node net library..
2/10/2026, 1:45:46 PM GMT [Modules] No module updates available.
splashScreen: update-check-finished true 0 false
splashScreen.launchMainWindow: false
Optional module ./ElectronTestRpc was not included.
Clearing GPU cache...
splashScreen.updateSplashState launching launching {}
splashScreen.webContentsSend: SPLASH_UPDATE_STATE SPLASH_UPDATE_STATE [ { status: 'launching' } ]
blackbox: 2/10/2026, 1:45:46 PM GMT 5 ✅ webContents.created web2 ""
13:45:46.150 › DiscordSplash.onStateUpdate: {"status":"launching"}
13:45:46.151 › Splash.onStateUpdate: {"status":"launching"}
Clearing code cache...
blackbox: 2/10/2026, 1:45:46 PM GMT 6 ✅ window.created win2 "Discord"
[ConnectivityTester xmr2jf] Sending DNS query: idt-xmr2jf-mlgnlst9.loc-en-gb.chk-webapp.res-err.err-403-status-403.dur-0.v1.dc-telemetry.net
blackbox: 2/10/2026, 1:45:46 PM GMT 7 ✅ webContents.did-finish-load web2
13:45:46.992 › Splash.updateCountdownSeconds: undefined
13:45:47.992 › Splash.updateCountdownSeconds: undefined
13:45:48.995 › Splash.updateCountdownSeconds: undefined
13:45:49.992 › Splash.updateCountdownSeconds: undefined
[81382:0210/134550.272686:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 1 times!

I’ve also tried :

discord --use-gl=swiftshader 

The output :

Discord 0.0.124
[81733:0210/134654.542011:ERROR:ui/gl/init/gl_factory.cc:103] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default)].
[81733:0210/134654.542786:ERROR:components/viz/service/main/viz_main_impl.cc:184] Exiting GPU process due to errors during initialization
(electron) 'session.getPreloads' is deprecated and will be removed. Please use 'session.getPreloadScripts' instead.
(electron) 'session.setPreloads' is deprecated and will be removed. Please use 'session.registerPreloadScript' instead.
Starting app.
Starting updater.
2/10/2026, 1:46:54 PM GMT [Modules] Modules initializing
2/10/2026, 1:46:54 PM GMT [Modules] Distribution: remote
2/10/2026, 1:46:54 PM GMT [Modules] Host updates: enabled
2/10/2026, 1:46:54 PM GMT [Modules] Module updates: enabled
2/10/2026, 1:46:54 PM GMT [Modules] Module install path: /home/jorgecpd/.config/discord/0.0.124/modules
2/10/2026, 1:46:54 PM GMT [Modules] Module installed file path: /home/jorgecpd/.config/discord/0.0.124/modules/installed.json
2/10/2026, 1:46:54 PM GMT [Modules] Module download path: /home/jorgecpd/.config/discord/0.0.124/modules/pending
splashScreen.initSplash(false)
blackbox: 2/10/2026, 1:46:54 PM GMT 0 

----------------------------------------------
[81760:0210/134654.636829:ERROR:ui/gl/init/gl_factory.cc:103] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default)].
[81760:0210/134654.637504:ERROR:components/viz/service/main/viz_main_impl.cc:184] Exiting GPU process due to errors during initialization
[81768:0210/134654.644474:ERROR:ui/gl/init/gl_factory.cc:103] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default)].
[81768:0210/134654.645109:ERROR:components/viz/service/main/viz_main_impl.cc:184] Exiting GPU process due to errors during initialization
blackbox: 2/10/2026, 1:46:54 PM GMT 1 Discord starting: {"releaseChannel":"stable","version":"0.0.124"}, modulepath: /home/jorgecpd/.config/discord/0.0.124/modules
[81776:0210/134654.652287:ERROR:ui/gl/init/gl_factory.cc:103] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default)].
blackbox: 2/10/2026, 1:46:54 PM GMT 2 ✅ webContents.created web1 "index.html"
[81776:0210/134654.652971:ERROR:components/viz/service/main/viz_main_impl.cc:184] Exiting GPU process due to errors during initialization
blackbox: 2/10/2026, 1:46:54 PM GMT 3 ✅ window.created win1 "discord"
(electron) 'console-message' arguments are deprecated and will be removed. Please use Event<WebContentsConsoleMessageEventParams> object instead.
13:46:54.738 › DiscordSplash.signalReady
splashScreen: SPLASH_SCREEN_READY
splashScreen.webContentsSend: SPLASH_SCREEN_QUOTE SPLASH_SCREEN_QUOTE [ 'Hold Tight — Loading Discord' ]
2/10/2026, 1:46:54 PM GMT [Modules] No updates to install
splashScreen: no-pending-updates
2/10/2026, 1:46:54 PM GMT [Modules] Checking for host updates.
splashScreen: checking-for-updates
splashScreen.updateSplashState checking-for-updates checking-for-updates {}
splashScreen.webContentsSend: SPLASH_UPDATE_STATE SPLASH_UPDATE_STATE [ { status: 'checking-for-updates' } ]
13:46:54.755 › DiscordSplash.onStateUpdate: {"status":"checking-for-updates"}
13:46:54.756 › Splash.onStateUpdate: {"status":"checking-for-updates"}
blackbox: 2/10/2026, 1:46:54 PM GMT 4 ✅ webContents.did-finish-load web1
[ConnectivityTester 9b1ijv] Sending DNS query: idt-9b1ijv-mlgnn9w6.loc-en-gb.chk-updaterdep.res-err.err-403-status-403.dur-0.v1.dc-telemetry.net
Error downloading with electron net: https://discord.com/api/updates/stable?platform=linux&version=0.0.124 HTTP Error: Status Code 403
Falling back to node net library..
2/10/2026, 1:46:55 PM GMT [Modules] Host is up to date.
2/10/2026, 1:46:55 PM GMT [Modules] Checking for module updates at https://discord.com/api/modules/stable/versions.json
13:46:55.738 › Splash.updateCountdownSeconds: undefined
Error downloading with electron net: https://discord.com/api/modules/stable/versions.json HTTP Error: Status Code 403
Falling back to node net library..
2/10/2026, 1:46:55 PM GMT [Modules] No module updates available.
splashScreen: update-check-finished true 0 false
splashScreen.launchMainWindow: false
Optional module ./ElectronTestRpc was not included.
Clearing GPU cache...
blackbox: 2/10/2026, 1:46:55 PM GMT 5 ✅ webContents.created web2 ""
splashScreen.updateSplashState launching launching {}
splashScreen.webContentsSend: SPLASH_UPDATE_STATE SPLASH_UPDATE_STATE [ { status: 'launching' } ]
Clearing code cache...
13:46:55.899 › DiscordSplash.onStateUpdate: {"status":"launching"}
13:46:55.899 › Splash.onStateUpdate: {"status":"launching"}
blackbox: 2/10/2026, 1:46:55 PM GMT 6 ✅ window.created win2 "Discord"
[ConnectivityTester 9b1ijv] Sending DNS query: idt-9b1ijv-mlgnnamn.loc-en-gb.chk-webapp.res-err.err-403-status-403.dur-0.v1.dc-telemetry.net
blackbox: 2/10/2026, 1:46:56 PM GMT 7 ✅ webContents.did-finish-load web2
13:46:56.738 › Splash.updateCountdownSeconds: undefined

Expected behavior

Discord should render its UI normally without a black window. It should work on Wayland with an AMD GPU (RADV / Mesa) using the official Manjaro package.

Workarounds / Flags tested

  • --disable-gpu --disable-software-rasterizer → fails to start (GPU access not allowed).
  • --enable-features=UseOzonePlatform --ozone-platform=x11 → still black window.
  • --use-gl=swiftshader → GPU process fails, window remains black.
  • Tried both the stable package and the previous version (before 0.0.124) → same issue.

Additional notes / questions

  • This seems to be an Electron + Wayland + AMD GPU issue.
  • Discord uses its own bundled Electron runtime.
  • Should this be reported upstream to Discord / Electron, or is there a Manjaro-specific fix?
    ~  inxi -zv8                                                                                                                                                                                                                             1 ✘ 
System:
  Kernel: 6.19.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.19-x86_64
    root=UUID=67c4e3fb-311e-4604-9383-d9cc274cf0fa rw rootflags=subvol=@
    quiet splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A info: frameworks v: 6.22.0
    wm: kwin_wayland vt: 2 dm: N/A Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG CROSSHAIR VIII FORMULA v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: 5002 date: 01/13/2025
Battery:
  ID-1: hidpp_battery_0 charge: 70% condition: N/A volts: 3.93 min: N/A
    model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
    serial: <filter> charging: status: discharging cycles: N/A
Memory:
  System RAM: total: 32 GiB available: 31.25 GiB used: 13.65 GiB (43.7%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 3200 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G Skill Intl
    part-no: F4-3200C14-8GFX serial: N/A
  Device-2: DIMM_A2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 3200 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G Skill Intl
    part-no: F4-3200C14-8GFX serial: N/A
  Device-3: DIMM_B1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 3200 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G Skill Intl
    part-no: F4-3200C14-8GFX serial: N/A
  Device-4: DIMM_B2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 3200 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G Skill Intl
    part-no: F4-3200C14-8GFX serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA201030
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 3359 min/max: 556/4854 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 3359 2: 3359 3: 3359
    4: 3359 5: 3359 6: 3359 7: 3359 8: 3359 9: 3359 10: 3359 11: 3359 12: 3359
    13: 3359 14: 3359 15: 3359 16: 3359 bogomips: 121609
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip
    user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
    vpclmulqdq wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
    xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900
    XTX/7900 GRE/7900M] vendor: ASUSTeK TUF Gaming driver: amdgpu v: kernel
    arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1
    empty: DP-2,DP-3,Writeback-1 bus-ID: 0d:00.0 chip-ID: 1002:744c
    class-ID: 0300
  Device-2: Logitech Logitech Webcam C925e driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.2.2:7
    chip-ID: 046d:085b class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu d-rect: 5760x2160 display-ID: 0
  Monitor-1: DP-1 pos: right model: LG (GoldStar) 27GN950 serial: <filter>
    built: 2021 res: mode: 3840x2160 hz: 120 scale: 170% (1.7) to: 2259x1271
    dpi: 163 gamma: 1.2 chroma: red: x: 0.682 y: 0.314 green: x: 0.267
    y: 0.686 blue: x: 0.149 y: 0.055 white: x: 0.314 y: 0.329
    size: 600x340mm (23.62x13.39") diag: 690mm (27.2") ratio: 16:9
    modes: 3840x2160, 1920x1080, 1280x720, 1024x768, 800x600, 720x480,
    640x480
  EDID-Errors: 1: bad sync value: bad horizontal values: min: 30 max: 15
  EDID-Warnings: 1: parse_edid: unknown tag 112
  Monitor-2: HDMI-A-1 pos: primary,left model: Idek Iiyama PLE2607WS
    serial: <filter> built: 2008 res: mode: 1920x1200 hz: 60 scale: 160% (1.6)
    to: 1200x1920 dpi: 89 gamma: 1.2 chroma: red: x: 0.647 y: 0.333 green:
    x: 0.282 y: 0.600 blue: x: 0.149 y: 0.071 white: x: 0.314 y: 0.329
    size: 550x344mm (21.65x13.54") diag: 649mm (25.5") ratio: 16:10
    modes: 1920x1200, 1920x1080, 1600x1200, 1680x1050, 1280x1024, 1440x900,
    1152x864, 1280x720, 1024x768, 832x624, 800x600, 720x576, 720x480,
    640x480, 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.5-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
    navi31 LLVM 21.1.6 DRM 3.64 6.19.0-1-MANJARO) device-ID: 1002:744c
    memory: 23.44 GiB unified: no display-ID: :0.0
  API: Vulkan v: 1.4.341 layers: 6 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7900 XTX (RADV NAVI31) driver: mesa radv v: 25.3.5-arch1.1
    device-ID: 1002:744c surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: radeontop wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0d:00.1 chip-ID: 1002:ab30 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0f:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech Logitech Webcam C925e driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.2.2:7
    chip-ID: 046d:085b class-ID: 0102 serial: <filter>
  API: ALSA v: k6.19.0-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion]
    vendor: ASUSTeK driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 1 link-max: lanes: 4 port: N/A bus-ID: 05:00.0 chip-ID: 1d6a:11b1
    class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: down mac: <filter>
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp7s0 state: down mac: <filter>
  IF-ID-1: br-466c45b29e42 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-3: wg0-mullvad state: unknown speed: 10000 Mbps duplex: full
    mac: N/A
  IP v4: <filter> scope: global
  IP v6: <filter> scope: global
  IP v6: <filter> virtual: stable-privacy proto kernel_ll scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:3 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
  Device-2: Microsoft Nano Transceiver v1.0 for Bluetooth
    driver: hid-generic,usbhid type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 3-3.1:5 chip-ID: 045e:0745 class-ID: 0300
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 8.3 TiB used: 2.61 TiB (31.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung model: SSD 990 PRO 4TB
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 57.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 4TB
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 56.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 830 Series
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 3B1Q scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 QVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE WH14NS40 rev: 1.05
    dev-links: cdrom
  Features: speed: 40 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 2.59 TiB size: 2.59 TiB (100.00%) used: 191.79 GiB (7.2%)
    fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:6 label: Manjaro root
    uuid: 67c4e3fb-311e-4604-9383-d9cc274cf0fa
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 32.1 MiB (6.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:4 label: EFI
    uuid: 5BFB-F55D
  ID-3: /home raw-size: 3.49 TiB size: 3.44 TiB (98.40%)
    used: 2.42 TiB (70.5%) fs: ext4 dev: /dev/nvme1n1p1 maj-min: 259:1
    label: Home uuid: 1763d5a3-375c-4e17-a4cf-f96bde772b42
  ID-4: /var/cache raw-size: 2.59 TiB size: 2.59 TiB (100.00%)
    used: 191.79 GiB (7.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:6
    label: Manjaro root uuid: 67c4e3fb-311e-4604-9383-d9cc274cf0fa
  ID-5: /var/log raw-size: 2.59 TiB size: 2.59 TiB (100.00%)
    used: 191.79 GiB (7.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:6
    label: Manjaro root uuid: 67c4e3fb-311e-4604-9383-d9cc274cf0fa
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100)
    zswap: yes compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 63.5 GiB used: 1.26 GiB (2.0%)
    priority: -1 dev: /dev/nvme0n1p2 maj-min: 259:5 label: Swap
    uuid: 2fb0f355-cde7-4eb9-9259-9822d28c5af2
Unmounted:
  ID-1: /dev/nvme0n1p4 maj-min: 259:7 size: 1013.73 GiB fs: btrfs label: N/A
    uuid: 2012bb20-12df-40ac-a630-2ed115853dc0
  ID-2: /dev/nvme1n1p2 maj-min: 259:2 size: 150 GiB fs: btrfs
    label: snapshots backup syst\xc3\xa8me
    uuid: e51dc2b8-8026-4865-99e5-09216373f6af
  ID-3: /dev/sda1 maj-min: 8:1 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-4: /dev/sda2 maj-min: 8:2 size: 118.5 GiB fs: ntfs label: N/A
    uuid: 648AA69E8AA66C6C
  ID-5: /dev/sda3 maj-min: 8:3 size: 743 MiB fs: ntfs label: N/A
    uuid: FADE7F8FDE7F4345
  ID-6: /dev/sdb1 maj-min: 8:17 size: 868 MiB fs: vfat label: N/A
    uuid: A567-7EF7
  ID-7: /dev/sdb2 maj-min: 8:18 size: 930.66 GiB fs: ext4 label: N/A
    uuid: f18e7382-b9e7-4ab1-84ec-8fc5127f31d3
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-5:2 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-5.3:4 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:18f3 class-ID: 0300
    serial: <filter>
  Device-2: 1-5.4:5 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 0b05:1872 class-ID: 0300
    serial: <filter>
  Device-3: 1-6:3 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-5: 3-2:2 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 174c:2074 class-ID: 0900
  Device-1: 3-2.1:4 info: Advanced Card Systems ACR38 SmartCard Reader
    type: smart card driver: N/A interfaces: 1 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 072f:90cc class-ID: 0b00
  Hub-6: 3-2.2:6 info: Texas Instruments TUSB8041 4-Port Hub ports: 4
    rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0451:8142
    class-ID: 0900
  Device-1: 3-2.2.2:7 info: Logitech Logitech Webcam C925e type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 046d:085b class-ID: 0102 serial: <filter>
  Device-2: 3-2.2.4:11 info: LG USA Monitor Controls
    type: HID,abstract (modem),CDC-data driver: cdc_acm,hid-generic,usbhid
    interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    chip-ID: 043e:9a8a class-ID: 0a00 serial: <filter>
  Hub-7: 3-3:3 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 174c:2074 class-ID: 0900
  Device-1: 3-3.1:5 info: Microsoft Nano Transceiver v1.0 for Bluetooth
    type: keyboard,mouse,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 045e:0745 class-ID: 0300
  Device-2: 3-3.2:8 info: HP HP Color LaserJet Pro M478f-9f type: printer
    driver: usblp interfaces: 5 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 2mA chip-ID: 03f0:c52a class-ID: 0701 serial: <filter>
  Hub-8: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-9: 4-2:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 8mA
    chip-ID: 174c:3074 class-ID: 0900
  Hub-10: 4-2.2:4 info: Texas Instruments TUSB8041 4-Port Hub ports: 4
    rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1
    chip-ID: 0451:8140 class-ID: 0900
  Hub-11: 4-3:3 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 8mA
    chip-ID: 174c:3074 class-ID: 0900
  Hub-12: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 5-3:2 info: Logitech Lightspeed Receiver
    type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c539 class-ID: 0300
  Hub-13: 6-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 51.0 C mobo: 41.0 C gpu: amdgpu temp: 59.0 C
    mem: 66.0 C
  Fan Speeds (rpm): cpu: 889 gpu: amdgpu fan: 616
Repos:
  Packages: 1739 pm: pacman pkgs: 1737 libs: 421 tools: pamac,yay pm: flatpak
    pkgs: 2
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.freedif.org/Manjaro/testing/$repo/$arch
    2: https://mirrors.ocf.berkeley.edu/manjaro/testing/$repo/$arch
    3: https://ftp.linux.org.tr/manjaro/testing/$repo/$arch
    4: https://codingflyboy.mm.fcix.net/manjaro/testing/$repo/$arch
    5: https://manjaro.mirrors.uk2.net/testing/$repo/$arch
    6: https://mirror.kku.ac.th/manjaro/testing/$repo/$arch
    7: https://mirror.komelt.dev/manjaro/testing/$repo/$arch
    8: https://mirror.csclub.uwaterloo.ca/manjaro/testing/$repo/$arch
    9: https://volico.mm.fcix.net/manjaro/testing/$repo/$arch
    10: https://mirrors.eric.ovh/manjaro/testing/$repo/$arch
    11: https://ftp.halifax.rwth-aachen.de/manjaro/testing/$repo/$arch
    12: https://kartolo.sby.datautama.net.id/manjaro/testing/$repo/$arch
    13: https://mirrors.manjaro.org/repo/testing/$repo/$arch
    14: https://nnenix.mm.fcix.net/manjaro/testing/$repo/$arch
    15: https://ftp.lysator.liu.se/pub/manjaro/testing/$repo/$arch
    16: https://mirror1.sox.rs/manjaro/testing/$repo/$arch
    17: https://mirrors.jlu.edu.cn/manjaro/testing/$repo/$arch
    18: https://mirror.truenetwork.ru/manjaro/testing/$repo/$arch
    19: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/testing/$repo/$arch
    20: https://mirror.nyist.edu.cn/manjaro/testing/$repo/$arch
    21: https://mirrors.ft.uam.es/manjaro/testing/$repo/$arch
    22: https://mirror.fcix.net/manjaro/testing/$repo/$arch
    23: https://cofractal-ewr.mm.fcix.net/manjaro/testing/$repo/$arch
    24: https://ba.mirror.garr.it/mirrors/manjaro/testing/$repo/$arch
    25: https://nocix.mm.fcix.net/manjaro/testing/$repo/$arch
    26: https://mirror.raiolanetworks.com/manjaro/testing/$repo/$arch
    27: https://manjaro.mirror.liquidtelecom.com/testing/$repo/$arch
    28: https://mirrors.sonic.net/manjaro/testing/$repo/$arch
    29: https://mirror.init7.net/manjaro/testing/$repo/$arch
    30: https://manjaro.mirror.garr.it/manjaro/testing/$repo/$arch
    31: https://mirrors.gigenet.com/manjaro/testing/$repo/$arch
    32: https://fosszone.csd.auth.gr/manjaro/testing/$repo/$arch
    33: https://manjaro.kurdy.org/testing/$repo/$arch
    34: https://mirrors.ucr.ac.cr/manjaro/testing/$repo/$arch
    35: https://mirrors.xtom.jp/manjaro/testing/$repo/$arch
    36: https://mirror.futureweb.be/manjaro/testing/$repo/$arch
    37: https://mirror.it4i.cz/manjaro/testing/$repo/$arch
    38: https://ftp.free.org/mirrors/repo.manjaro.org/repos/testing/$repo/$arch
    39: https://forksystems.mm.fcix.net/manjaro/testing/$repo/$arch
    40: https://mirror.netcologne.de/manjaro/testing/$repo/$arch
    41: https://mirror.xenyth.net/manjaro/testing/$repo/$arch
    42: https://mirror.dimensiondata.com/mirrors/manjaro.org/testing/$repo/$arch
    43: https://manjaro.grena.ge/testing/$repo/$arch
    44: https://mirrors.dotsrc.org/manjaro/testing/$repo/$arch
    45: https://irltoolkit.mm.fcix.net/manjaro/testing/$repo/$arch
    46: https://ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/testing/$repo/$arch
    47: https://ct.mirror.garr.it/mirrors/manjaro/testing/$repo/$arch
    48: https://mirror.23m.com/manjaro/testing/$repo/$arch
    49: https://ftpmirror1.infania.net/mirror/manjaro/testing/$repo/$arch
    50: https://mirrors.cicku.me/manjaro/testing/$repo/$arch
    51: https://mirror.easyname.at/manjaro/testing/$repo/$arch
    52: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/testing/$repo/$arch
    53: https://mirror.telepoint.bg/manjaro/testing/$repo/$arch
    54: https://mirror.2degrees.nz/manjaro/testing/$repo/$arch
    55: https://ftp.tu-chemnitz.de/pub/linux/manjaro/testing/$repo/$arch
    56: https://mirrors.tuna.tsinghua.edu.cn/manjaro/testing/$repo/$arch
    57: https://manjaro.mirrors.lavatech.top/testing/$repo/$arch
    58: https://coresite.mm.fcix.net/manjaro/testing/$repo/$arch
    59: https://manjarolinux-mirror.cloud.mu/testing/$repo/$arch
    60: https://ftp.belnet.be/mirrors/manjaro/repos/testing/$repo/$arch
    61: https://muug.ca/mirror/manjaro/testing/$repo/$arch
    62: https://southfront.mm.fcix.net/manjaro/testing/$repo/$arch
    63: https://gsl-syd.mm.fcix.net/manjaro/testing/$repo/$arch
    64: https://mirror.datacenter.by/pub/mirrors/manjaro/testing/$repo/$arch
    65: https://mirror.dc.uz/manjaro/testing/$repo/$arch
    66: https://mirror.xeonbd.com/manjaro/testing/$repo/$arch
    67: https://mirrors.ustc.edu.cn/manjaro/testing/$repo/$arch
    68: https://mirrors.atlas.net.co/manjaro/testing/$repo/$arch
    69: https://mirror.dkm.cz/manjaro/testing/$repo/$arch
    70: https://mirrors2.manjaro.org/testing/$repo/$arch
    71: http://ftp.uni-kl.de/pub/linux/manjaro/testing/$repo/$arch
    72: https://mirror.meowsmp.net/manjaro/testing/$repo/$arch
    73: https://ohioix.mm.fcix.net/manjaro/testing/$repo/$arch
    74: https://linorg.usp.br/manjaro/testing/$repo/$arch
    75: https://mirror.vinehost.net/manjaro/testing/$repo/$arch
    76: https://mirror.bakertelekom.fr/manjaro/testing/$repo/$arch
    77: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/testing/$repo/$arch
    78: https://edgeuno-bog2.mm.fcix.net/manjaro/testing/$repo/$arch
    79: https://ftp.gwdg.de/pub/linux/manjaro/testing/$repo/$arch
    80: https://manjaro.mirror.wearetriple.com/testing/$repo/$arch
    81: https://mirror.math.princeton.edu/pub/manjaro/testing/$repo/$arch
    82: https://repo.ialab.dsu.edu/manjaro/testing/$repo/$arch
    83: https://manjaro.ynh.ovh/testing/$repo/$arch
    84: https://mirror.alwyzon.net/manjaro/testing/$repo/$arch
    85: https://ftp.psnc.pl/linux/manjaro/testing/$repo/$arch
    86: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/testing/$repo/$arch
    87: https://mirror.aarnet.edu.au/pub/manjaro/testing/$repo/$arch
    88: https://mirror.kamtv.ru/manjaro/testing/$repo/$arch
    89: https://mirror.koddos.net/manjaro/testing/$repo/$arch
    90: https://ftp.caliu.cat/pub/distribucions/manjaro/testing/$repo/$arch
    91: https://mirrors.sjtug.sjtu.edu.cn/manjaro/testing/$repo/$arch
    92: https://mirror.bouwhuis.network/manjaro/testing/$repo/$arch
    93: https://ftp.snt.utwente.nl/pub/linux/manjaro/testing/$repo/$arch
    94: https://opencolo.mm.fcix.net/manjaro/testing/$repo/$arch
    95: https://mirror.phoepsilonix.love/manjaro/testing/$repo/$arch
    96: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/testing/$repo/$arch
    97: https://manjaro.mirror-services.net/pub/testing/$repo/$arch
    98: https://ziply.mm.fcix.net/manjaro/testing/$repo/$arch
    99: https://mirror.alpix.eu/manjaro/testing/$repo/$arch
    100: https://ask4.mm.fcix.net/manjaro/testing/$repo/$arch
    101: https://manjaro.c3sl.ufpr.br/testing/$repo/$arch
    102: https://mirror.yandex.ru/mirrors/manjaro/testing/$repo/$arch
Processes:
  CPU top: 5 of 730
  1: cpu: 200% command: ps pid: 88366 mem: 4.32 MiB (0.0%)
  2: cpu: 29.3% command: baloo_file_extractor pid: 2516
    mem: 1245.5 MiB (3.8%)
  3: cpu: 6.8% command: firefox pid: 54269 mem: 1259.9 MiB (3.9%)
  4: cpu: 6.4% command: exe pid: 85777 mem: 165.6 MiB (0.5%)
  5: cpu: 5.9% command: firefox pid: 78591 mem: 568.3 MiB (1.7%)
  Memory top: 5 of 730
  1: mem: 1259.9 MiB (3.9%) command: firefox pid: 54269 cpu: 6.8%
  2: mem: 1245.5 MiB (3.8%) command: baloo_file_extractor pid: 2516
    cpu: 29.3%
  3: mem: 1169.6 MiB (3.6%) command: pamac-manager pid: 63045 cpu: 0.2%
  4: mem: 997.4 MiB (3.1%) command: baloorunner pid: 14483 cpu: 0.0%
  5: mem: 889.3 MiB (2.7%) command: plasmashell pid: 1931 cpu: 0.6%
Info:
  Processes: 730 Power: uptime: 18h 29m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 2 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.48 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 259 default: graphical
    tool: systemctl
  Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.40

From what I read here over the times … Discord needs to always be at the current/newest version.

And when installed from the Manjaro repositories - which might not provide that newest version at all times - it will fail when the installed version is not that current version.

And the thus installed instance cannot be updated via the “in program” update mechanism.

I guess you either need do wait
or switch to a more current branch of Manjaro (testing or unstable)
or install Discord in another way - so that it can be updated whenever they update. :man_shrugging:

1 Like

Well, considering that discord is rather peculiar about updating and refuses to work whenever its own developers release a new version until you’ve updated the application, the general recommendation in Manjaro is to use the FlatPak instead.

That said, given that FlatPaks are containerized and come bundled with their own set of version-specific dependencies, I would recommend trying the FlatPak and seeing whether that one works.

If it does work, then we know that there is a problem with the electron version packaged by Arch, which is where the discord in Manjaro comes from, and then we might be able to get the Arch packager to update his package.


All three branches carry the same version of discord, so switching branches won’t be a solution in this case.

Thank you for your response. In this case, though, it isn’t a “need update” situation, I am familiar with those. The package was updated yesterday or so, it is up-to-date, as far as I understand. When it needs an update, it asks the user to download the .tar.gz, which isn’t the case this time around.

In that case I can’t be of any help at all. Sorry!
… I do not even know the program from personal experience - have never used it …

Thank you for your suggestion.

I tried the flatpak variant of Discord, and it works. However, it is the same exact version than the one in Manjaro’s repo’s.

Whenever I can, I avoid using flatpak packages. I’d like to continue using the one in Manjaro’s repo’s.

Then it would indeed appear to be an issue with the dependencies of discord, and thus a packaging error. Possibly the included electron, but it may also be something else.

I understand, but given that discord is proprietary software, and that its own developers maintain their infamous “We’re going to break the version you’ve got installed until you install the newer one” attitude, the recommendation for discord in particular is to use the FlatPak instead. :wink:

1 Like

They are a pain, I know. But in this case, the version shipped in Flatpak and in Manjaro Repo’s is the same.

It might be worth updating the Discord package in the official repos to a newer Electron version or reviewing the packaging for Wayland compatibility.

Is there anything more I should do at this point?

Well, we ourselves don’t package discord. We take over that package from Arch verbatim.

I don’t see what. :grin:

Well, will Manjaro’s maintainers contact the Arch maintainers, or is it me who should do it? What would be the best course of action?

No one will be contacting Arch Package Maintainers as it’s not a packaging issue. All the package does is unpack the official tarball.

Either way, I can’t reproduce the issue on GNOME. I haven’t seen anyone else report any issues, so that points to something locally on your system.

Thanks for the clarification. I understand that the Manjaro package just unpacks the official tarball.

I’m reporting this because the issue seems specific to my setup: KDE Plasma on Wayland with RADV/Mesa.
The Discord window opens but remains completely black/empty, even with the latest official tarball.

I tested the Flatpak version, and it works correctly under the same environment, which suggests the issue is related to how Electron interacts with Wayland/RADV in my system setup, rather than a packaging problem.

Has anyone experienced similar behavior under KDE/Wayland with AMD GPUs? Are there known Electron flags or Mesa settings that might resolve this?

Create a new User account for testing:

As was previously alluded to, your issue is likely specific to your environment – to rule out the possibility, create a new User account for testing purposes.

Once this account is created, login to the new User account, and test any application(s) concerned to verify whether the problem persists in a fresh environment.

This is an important troubleshooting step. If the application launches as expected in the fresh environment, this helps in determining whether the problem is limited to your usual User account.

This information is invaluable for those wishing to help.

1 Like

Thank you for the suggestion.

I tested with a fresh user account as recommended, and Discord works correctly there. Mullvad is not installed in that account.

This confirms the issue is limited to my main user account.

Back in my main account, I completely disabled Mullvad and tested again — the issue persisted.

I then performed the following reset:

pkill discord
rm -rf ~/.config/discord
rm -rf ~/.cache/discord

After that, Discord launched properly and was able to complete its update process. Before this reset, it consistently stalled and eventually reported:
“WebApp timed out loading (timeout=60s)”.

From what I can observe, the host binary was already up to date, but something in the local Discord state (configuration, modules metadata, or cache) appears to have become inconsistent. Removing the user-level config and cache restored a clean state and resolved the issue.

This is the second time this has happened on my system, which suggests that occasionally the local Discord state becomes corrupted after an update.

If anyone has insight into what might cause Discord’s per-user update or cache state to become inconsistent under KDE Wayland, I’d appreciate any pointers.

1 Like