Skip to content

[Bug]: Wayland rendering falls back to XWayland #1293

Description

@kernitus

NegPy version / build

0.63.0

OS

Arch Linux

Scanner

N/A (not a scan-related issue)

Scanner model / details

No response

Light source

N/A

Correction mode

N/A

Input ICC profile (if any)

No response

Relevant process-tab settings

No response

What happened

NegPy 0.63.0 runs through XWayland on my Wayland desktop, making text blurry on my laptop screen at 150% scaling. Moving the window to my external monitor at 100% scaling makes it sharp.

I traced the cause to rendercanvas and tested a local rebuild with its unreleased upstream fix. The rebuilt application runs natively on Wayland and the text is now sharp.

Environment:

  • Hyprland 0.56.2
  • NegPy 0.63.0, Linux AppImage
  • Laptop: 1920 × 1200 at 150% scaling
  • External monitor: 1920 × 1080 at 100% scaling
  • AMD Radeon 780M with RADV Vulkan

NegPy’s AppImage launcher sets QT_QPA_PLATFORM="wayland;xcb", but its pinned rendercanvas 2.6.3 dependency unconditionally overwrites this with xcb when it detects a Wayland session. With NegPy’s display.qt_platform set to auto, that override remains active.

Upstream has merged rendercanvas PR #233, commit 67b9f479ebb44bbdfcdf9be3e2bb45591597f0af, which adds native Wayland support for Qt and respects an explicit platform choice. The latest PyPI release, 2.7.2 still predates this fix.

I rebuilt NegPy 0.63.0 with that rendercanvas commit. Now it seems to run on native wayland without blurry text. So really we just need to wait for rendercanvas to release and then update that dependency

Source file

N/A

Screenshots

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions