[Bug]: bad quality of desktop screen

未关闭
#1,465 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
18/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
electron, typescript

调研方向

The payload gives only a screenshot and a vague report of poor quality in the editor and in the rendered output on Wayland; no file or entry point is named. Start by reproducing the editor preview and export on Linux under Wayland and compare with another platform to isolate where the resolution drops. Done would mean a reproduction plus a confirmed cause, which the maintainers would need to agree on before any fix.

由索引模型根据 Issue 内容生成。

描述

bug
Search existing issues
  • I have searched the existing issues
Describe the bug
Image
Expected behavior

In editor bad quality, after render also bad quality on desktop screen

To Reproduce

No response

Screenshots

No response

OS

None

OS Version

CachyOS x86_64 (Linux 7.2.9-1-cachyos) + niri 26.04 (Wayland)

Other OS

No response

Browser

None

Browser Version

No response

Other Browser

No response

Device Type

None

Other Device

No response

Additional context
                             dealenx@cachyos-asus-tuf-x8664
       ...........           ------------------------------
      /,,,,...../              OS  CachyOS x86_64
     /,,,..,,../   ()           Kernel  Linux 7.2.9-1-cachyos
    /,,,,../                   Uptime  8 hours
   /,,,.../     /'\            Packages  1301 (pacman)
  /,...../      \,/            Shell  fish 4.9.3
  \,,,,,,\\             _      WM  niri 26.04 (Wayland)
   \,,....\\           / \      Term  alacritty 0.17.0
    \...,..\\          \_/     󰻠 CPU  AMD Ryzen 5 3550H (8) @ 3.70 GHz
     \..,,,,,,,,,,,,/          󰢮 GPU  NVIDIA GeForce GTX 1650 Mobile / Max-Q [Discrete]
      \,,........,,/           󰍛 Memory  14.46 GiB / 29.30 GiB (49%)
                               󰓡 Swap  2.52 GiB / 29.30 GiB (9%)
                               󰋊 Disk (/)  329.59 GiB / 472.94 GiB (70%) - btrfs
主要语言
TypeScript
星标
3.7k
派生
231
平均合并
16 小时 31 分钟
30 天内合并 PR
281

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

getopenscreen/openscreen 的其他 Issue

查看 getopenscreen/openscreen 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。