Readwyn 0.1.0

Read ebooks on Linux with Wayland or X11

Both work. Readwyn runs in a Wayland session and in an X11 one, and it relies only on services that every major desktop provides. Tests covered Wayland with GNOME and KDE Plasma, and X11 with GNOME (the arm64 post lists each system). The two sessions differ in how the 3D library takes the mouse, and on GNOME under Wayland a window that the tray icon opens doesn't come to the front. Who draws the window frame depends on the desktop rather than the session.

Window controls

GNOME on Wayland doesn't draw title bars for apps, so Readwyn draws its own: minimize, maximize and close, three small circles at the right end of each window's top bar. The library, the reader, the comic reader and Settings all have them. GNOME's X11 session shows the same controls; the Linux screenshots on this site were taken there.

The Readwyn library on Linux: at the top right, after the search and Add books, three round window controls for minimize, maximize, and close
The window controls at the right end of the top bar

The top bar then behaves like a title bar:

  • Dragging an empty part of it, or the empty strip at the top of the sidebar, moves the window once the pointer has travelled 4 px.
  • Double-clicking there maximizes the window, or restores it.
  • Right-clicking there opens the system's window menu.
  • A 5 px band along each edge resizes the window, and each corner catches the pointer from 16 px along both of its edges.

A maximized or tiled window has no border, and its tiled edges don't resize. Closing the library window quits the app, as on the Mac.

Some systems draw the decorations themselves: an X11 window manager without a compositor, say, or a Wayland compositor that keeps its own title bars. Readwyn then leaves the frame to them and draws no controls, border or resize bands.

Every window carries the app ID com.readwyn.Readwyn, the same name as the menu entry, so the desktop matches each window to that entry and shows Readwyn's icon for it.

Mouse look in the 3D library

Click the scene in the 3D library and the pointer locks: a crosshair appears and the mouse turns the view. Esc frees it again. Wayland and X11 handle the lock differently:

  • Wayland. The compositor locks the pointer and reports its motion without acceleration. When you press Esc, the cursor comes back in the middle of the window. A compositor that lacks zwp_pointer_constraints_v1 and zwp_relative_pointer_v1 leaves the pointer free: the crosshair shows, but the mouse doesn't turn the view.
  • X11. Readwyn keeps the cursor inside the window and turns the view by the raw motion of the mouse or touchpad, skipping the X server's acceleration.

On 25 October 2026 this was tested on Ubuntu 24.04 with GNOME 46, with a virtual mouse that moved 10 counts at a time, forty times. On both Wayland and X11 the view turned exactly 10 points per move. On Wayland the compositor reported 11.07 points of accelerated motion for each of those moves; the view uses the unaccelerated 10.

Reduced motion

If you turn animations off in your desktop's settings, Readwyn tones its own motion down too, as it does with Reduce Motion on a Mac. In the 3D library, a glide to a book becomes a short fade, and Settings › 3D library says so: “With animations off in the settings of the desktop, a glide to a book is a short fade.” Readwyn reads the setting through the settings portal, so GNOME's enable-animations set to false and KDE's AnimationDurationFactor at 0 both count.

When a window won't come forward on GNOME

The background server can open a page in the running app, for example “Connected devices…” from its icon in the system tray. On GNOME under Wayland, though, the window doesn't come to the front this way. In a test, the app opened Settings › Other devices as asked, and GNOME showed a notification that “Other devices” is ready instead of raising the window.