flathub / io.github.cudatext.CudaText-Qt

https://flathub.org/apps/details/io.github.cudatext.CudaText-Qt
0 stars 0 forks source link

Flatpak version: keyboard input doesn't work #16

Open Alexey-T opened 2 days ago

Alexey-T commented 2 days ago

Please see user report: https://github.com/Alexey-T/CudaText/issues/5739 Keyboard input don't work in the Flatpak version, while in DEB version all is ok.

JordanL2 commented 2 days ago

Can't reproduce, editing a file with the flatpak version works for me, keyboard input works. I'd need more info about the exact situation or environment.

Alexey-T commented 2 days ago

@atarax42 Pls show your system info.

atarax42 commented 2 days ago
System:
  Host: latitudio Kernel: 6.8.0-47-generic arch: x86_64 bits: 64
  Desktop: Cinnamon v: 6.2.9 Distro: Linux Mint 22 Wilma
Machine:
  Type: Laptop System: Dell product: Latitude 7490 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 0KP0FT v: A00 serial: <superuser required> UEFI: Dell
    v: 1.19.0 date: 02/23/2021
Battery:
  ID-1: BAT0 charge: 55.6 Wh (100.0%) condition: 55.6/60.0 Wh (92.7%)
CPU:
  Info: quad core Intel Core i5-8350U [MT MCP] speed (MHz): avg: 802
    min/max: 400/3600
Graphics:
  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
  Device-2: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo
    type: USB
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
    resolution: 1600x900~60Hz
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.0.9-0ubuntu0.2
    renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
Network:
  Device-1: Intel Ethernet I219-LM driver: e1000e
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi
Drives:
  Local Storage: total: 238.47 GiB used: 124.38 GiB (52.2%)
Info:
  Memory: total: 8 GiB available: 7.63 GiB used: 3.32 GiB (43.5%)
  Processes: 300 Uptime: 1d 17h 6m Shell: Bash inxi: 3.3.34
JordanL2 commented 2 days ago

Can you provide exact steps to reproduce? As I say, editing a file works fine for me. What location is the file in?

atarax42 commented 2 days ago

I installed the flatpak on another system and there files can be edited. My idea is now that it might be related to Wayland. A few days ago I ran my machine with a Wayland session (without success) and switched to regular X after that. But maybe something was changed by Wayland. I don't know.

JordanL2 commented 2 days ago

I'm using Plasma Wayland, but it's possible there's an issue with Cinnamon Wayland. Can you switch Wayland to X11 and see if the issue persists?

atarax42 commented 2 days ago

In my case the issue is valid for Wayland and for X11. Might be related or not. I had the idea of this causality because the Wayland session was the only "exotic" task I performed with my machine before the installation of CudaText. And Wayland is very buggy with Cinnamon, so I thought something got damaged. I don't know.