67 lines
3.2 KiB
HTML
67 lines
3.2 KiB
HTML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
|
<head>
|
|
<!-- 2025-08-08 Fri 21:51 -->
|
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
<title>Wacom With Arch</title>
|
|
<meta name="generator" content="Org Mode" />
|
|
|
|
<link rel="stylesheet" href="https://gongzhitaao.org/orgcss/org.css" /> <link rel="stylesheet" href="/assets/style.css" /> <script src="/assets/script.js" defer></script>
|
|
</head>
|
|
<body>
|
|
<div id="preamble" class="status">
|
|
|
|
<div class="banner-header">
|
|
<a href="/"> <img src="/assets/gr.png" alt="Site Logo" class="banner-logo" /> </a>
|
|
<nav>
|
|
<a href="/">Home | </a>
|
|
<a href="/posts/posts-list.html">Posts | </a>
|
|
<a href="/blogs/blogs-list.html">Blogs | </a>
|
|
<a href="/contact.html">Contact</a>
|
|
</nav>
|
|
</div>
|
|
<div id="updated">Updated: 2025-08-08 Fri 21:06</div>
|
|
</div>
|
|
<div id="content" class="content">
|
|
<div id="outline-container-orgb3d6851" class="outline-2">
|
|
<h2 id="orgb3d6851">Wacom With Arch</h2>
|
|
<div class="outline-text-2" id="text-orgb3d6851">
|
|
<p>
|
|
I purchased a <a href="https://www.wacom.com/en-gb/products/one-by-wacom">One by Wacom</a> tablet almost 2 years ago now and it works flawlessly in both Windows and MacOS and even in most Linux distros with some configuration.
|
|
</p>
|
|
|
|
<p>
|
|
However with Arch and Hyprland, there were some issues related to the <code>xserver</code> it was running on. The X input driver module (e.g. xf86-input-wacom) is linked into the X server which in turn is in charge of rendering and generic input events. Hyprland on the other hand uses the Wayland display server protocol (replacement for the X protocol) hence why there is difficulty in input mapping.
|
|
</p>
|
|
|
|
<p>
|
|
I came across this issue as I was able to get the tablet to work across multiple monitors (mapping to a single one) through the <code>xsetwacom</code> function - which, at the time I was using Ubuntu. But with Hyprland there needs to be some manual intervention. I came across this <a href="https://thomaspurnell.com/003_wacom_graphics_hyprland/wacom_hyprland.html">post</a> which explains nicely how to map the tablet to a single monitor. I took this approach with a slight configuration; in my <code>hyprland.conf</code> file, I simply added the following line:
|
|
</p>
|
|
|
|
<div class="org-src-container">
|
|
<pre class="src src-nil">exec-once = hyprctl keyword "device[wacom-one-by-wacom-m-pen]:output" "DP-1"
|
|
</pre>
|
|
</div>
|
|
|
|
<p>
|
|
which mapped the device to the primary monitor DP-1.
|
|
</p>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div id="postamble" class="status">
|
|
<footer>
|
|
<div class="copyright-container">
|
|
<div class="copyright">
|
|
Copyright © 2022-2025 Zaine Qayyum. All rights reserved unless otherwise noted.</div></div>
|
|
<div class="generated">
|
|
Created with <a href="https://www.gnu.org/software/emacs/">Emacs</a> 30.1 (<a href="https://orgmode.org">Org</a> mode 9.7.11) on <a href="https://www.archlinux.org/">Arch</a> <a href="https://www.gnu.org">GNU</a>/<a href="https://www.kernel.org/">Linux</a>
|
|
</div>
|
|
</footer>
|
|
</div>
|
|
</body>
|
|
</html>
|