Bug 515055 - Cannot open episodes using touch on a touch-supported display
Summary: Cannot open episodes using touch on a touch-supported display
Status: REPORTED
Alias: None
Product: kasts
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: KDE Linux Linux
: NOR minor
Target Milestone: ---
Assignee: bart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-25 13:24 UTC by Extinct Dodo
Modified: 2026-01-25 17:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screen recording of the issue (3.43 MB, video/webm)
2026-01-25 13:24 UTC, Extinct Dodo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Extinct Dodo 2026-01-25 13:24:00 UTC
Created attachment 188866 [details]
Screen recording of the issue

SUMMARY

Using touch does not open an episode in kasts, but touchpad/mouse works fine


STEPS TO REPRODUCE
1. Navigate to the Episodes tab to play an episode
2. Touch the desired episode when using a touch-supported display

OBSERVED RESULT
The episode is selected



EXPECTED RESULT
The episode should be opened in its new tab


SOFTWARE/OS VERSIONS
Operating System: KDE Linux 2026-01-25
KDE Plasma Version: 6.6.80
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.1
Kernel Version: 6.18.6-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics

APP VERSION
Kasts: 25.12.1
KDE Flatpak runtime (Wayland)
KDE Frameworks: 6.22.0
Qt: Using 6.10.1 and built against 6.10.1
Flatpak
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.18.6-zen1-1-zen


ADDITIONAL INFORMATION
Please refer to the video to fully understand what I mean
Comment 1 bart 2026-01-25 16:12:52 UTC
Enabling/disabling touch should be a setting in plasma, I think.  It's been a while since I looked into it.

In general, enabling touch controls is done at the toolkit level, so that qt6 in this case.  There's not much the app itself can do to override toolkit-level settings. There might be environment variables that you can use to override the defaults when launching the app from the command line.

But, IIRC, there should be a toggle somewhere in KDE plasma settings to enable touch control in a system-wide manner.

PS: Unfortunately, I'm not really able to test this since I don't own a device with a touchscreen. Is this a laptop? And is it a native package or the flatpak version?
Comment 2 Extinct Dodo 2026-01-25 16:58:41 UTC
(In reply to bart from comment #1)
> Enabling/disabling touch should be a setting in plasma, I think.  It's been
> a while since I looked into it.
> 
> In general, enabling touch controls is done at the toolkit level, so that
> qt6 in this case.  There's not much the app itself can do to override
> toolkit-level settings. There might be environment variables that you can
> use to override the defaults when launching the app from the command line.
> 
> But, IIRC, there should be a toggle somewhere in KDE plasma settings to
> enable touch control in a system-wide manner.
> 
> PS: Unfortunately, I'm not really able to test this since I don't own a
> device with a touchscreen. Is this a laptop? And is it a native package or
> the flatpak version?

Touch works flawlessly across Plasma and its various apps. In fact, even on Kasts I had no problems with touch except for this little issue, so I'm not sure if it is a toolkit problem, but I know very little about these things. I'm using a 2-in-1 laptop with KDE Linux, so I have installed the app through flatpak.
Comment 3 bart 2026-01-25 17:08:56 UTC
Thanks for the additional info.

Sounds like it could be that flatpak containerization is not allowing that setting through.

I'll try to see if I can reproduce it somehow.