Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Workspace" button doesn't work on touch screen #992

Open
ShamrockLee opened this issue Jan 31, 2025 · 0 comments · May be fixed by #1010
Open

"Workspace" button doesn't work on touch screen #992

ShamrockLee opened this issue Jan 31, 2025 · 0 comments · May be fixed by #1010
Labels
bug Undesirable behavior touchscreen Issue is related to touch screen functionality

Comments

@ShamrockLee
Copy link

ShamrockLee commented Jan 31, 2025

Describe the bug
The top-left "Workspace " button brings users to GNOME's workspaces-and-dock page with a single click. Touchpad tapping and pen (stylus) clicking triger the button as well, but not touch screen tapping.

The same button works on touch screen in vanilla GNOME (without the PaperWM GNOME extension).

I suspect that the button is shadowed by the swipe-tiling-windows functionality mentioned in #804, but the "Windows focus mode" button seems working well on touch screen.

I'm willing to work on this issue, but I'm still familliarizing myself with this project. Could someone hint me about which pieces of code to look into?

To Reproduce
Steps to reproduce the behavior:

  1. Set up PaperWM on a device with a touch screen.
  2. Tap on the top-left "Workspace 1" button.
  3. See the button changes color during tapping but no page switching happens.

Expected behavior
Tapping the "Workspace " button on a touch screen should bring the user to the GNOME's workspace-and-dock page, just like mouse-clicking and touch-pad tapping the same button.

Screenshots
If applicable, add screenshots to help explain your problem.

System information:
Please provide system information:

  • if you installed PaperWM via extensions.gnome.org please open PaperWM settings and select the About tab (last tab) and click the Copy to Clipboard button and paste the information below, or;

  • if you installed via source code, please execute ./gather-system-info.sh in you PaperWM clone and paste the information below

I installed PaperWM via Home Manager's gnome-shell module and the following configuration:

{ config, lib, pkgs, ... }:
{
  programs.gnome-shell = {
    enable = true;

    extensions = [
      # Kimpanel
      {
        package = pkgs.gnomeExtensions.kimpanel;
      }
      # PaperWM
      {
        package = pkgs.gnomeExtensions.paperwm;
      }
    ];
  };
}

nix-info -m output:

  • system: "x86_64-linux"
  • host os: Linux 6.12.5, NixOS, 24.11 (Vicuna), 24.11.20241216.3945713
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.24.10
  • nixpkgs: /nix/store/wj2qla569hnxwqfc26imv5hqbxc1rc27-source
Distribution: NixOS 24.11
GNOME Shell: 47.1
Display server: Wayland
PaperWM version: (GNOME Extension version 134)
Enabled extensions (installed):
- [email protected]
- [email protected]
Extensions listed with `gnome-extensions list`:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
native-window-placement@gnome-shell-extensions.gcampax.github.com
[email protected]
screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Additional context
The "Workspace " button screenshot:
The "Workspace <n>" button screenshot

@ShamrockLee ShamrockLee added the bug Undesirable behavior label Jan 31, 2025
@Thesola10 Thesola10 added the touchscreen Issue is related to touch screen functionality label Mar 6, 2025
@Thesola10 Thesola10 linked a pull request Mar 27, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Undesirable behavior touchscreen Issue is related to touch screen functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants