https://bugs.kde.org/show_bug.cgi?id=411877
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.27
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=411877
Nicolas Fella changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=411877
Nicolas Fella changed:
What|Removed |Added
CC||m...@nueljl.in
--- Comment #27 from Nicolas Fel
https://bugs.kde.org/show_bug.cgi?id=411877
Bug Janitor Service changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #25 from lo...@kde.bt.alestan.publicvm.com ---
That appears to work, will verify next time it connects itself to the wrong
screen. If you get it connected to the correct screen, you can get the current
value via `qdbus org.kde.KWin /org/kde/
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #24 from David Sutton ---
So the first thing I had to do was find out which event was related to the
touch screen - in my case event4 was the one I needed: "qdbus org.kde.KWin
/org/kde/KWin/InputDevice/event4 org.freedesktop.DBus.Properties.
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #23 from lo...@kde.bt.alestan.publicvm.com ---
(In reply to David Sutton from comment #22)
> FWIW: I was reading through the notes on the merge request when I noticed a
> comment saying that the ability to set it was already in there, it just
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #22 from David Sutton ---
FWIW: I was reading through the notes on the merge request when I noticed a
comment saying that the ability to set it was already in there, it just wasn't
exposed via a UI. I was able to find the input device via DB
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #21 from lo...@kde.bt.alestan.publicvm.com ---
That is correct. I cannot think of any use case that is made *worse* by this
change, but it does not solve the underlying problem. I'm not sure if the
additional code complexity is worth catchi
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #20 from David Sutton ---
Looking at the possible merge request, it seems to make two assumptions - that
you only have two possible screens and that the screen isn't reporting any
physical dimensions - which is likely to fix one use case but
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #19 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/3032
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #18 from Oliver Sander ---
(In reply to Oliver Sander from comment #14)
> I just checked again. The input really is split across the two screens.
I checked again yesterday, with an updated stack from Debian testing. This
time, the input wa
https://bugs.kde.org/show_bug.cgi?id=411877
j...@j3l7h.de changed:
What|Removed |Added
CC||j...@j3l7h.de
--- Comment #17 from j...@j3l7h.de
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #16 from lo...@kde.bt.alestan.publicvm.com ---
(In reply to Abel Yang from comment #15)
> I can reproduce this bug on 5.24.5 (Fedora 36 Kernel 5.18.6). In my case, I
> have an external touchscreen connected to a laptop, both screens are
> 192
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #15 from Abel Yang ---
I can reproduce this bug on 5.24.5 (Fedora 36 Kernel 5.18.6). In my case, I
have an external touchscreen connected to a laptop, both screens are 1920x1080.
Laptop: Thinkpad T470s (Mesa Intel HD 620)
Touchscreen HID de
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #14 from Oliver Sander ---
I just checked again. The input really is split across the two screens.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #13 from Nicolas Fella ---
Gnome seems to have a similar heuristic (which may or may not produce better
results), but also has a config entry for manually mapping touchscreens to
outputs:
https://github.com/GNOME/gsettings-desktop-schemas/bl
https://bugs.kde.org/show_bug.cgi?id=411877
Nicolas Fella changed:
What|Removed |Added
CC||nicolas.fe...@gmx.de
--- Comment #12 from Nicol
https://bugs.kde.org/show_bug.cgi?id=411877
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #11 fro
https://bugs.kde.org/show_bug.cgi?id=411877
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
--- Comment #10 from Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=411877
David Sutton changed:
What|Removed |Added
CC||kant...@gmail.com
--- Comment #9 from David Sutt
https://bugs.kde.org/show_bug.cgi?id=411877
lo...@kde.bt.alestan.publicvm.com changed:
What|Removed |Added
Version|5.16.4 |5.20.4
--- Comment #5 from l
https://bugs.kde.org/show_bug.cgi?id=411877
Vlad Zahorodnii changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #6 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=411877
Mathieu Jobin changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #3 from lo...@kde.bt.alestan.publicvm.com ---
So I finally had a bit more time to dig into this, with a bit of grepping, I
managed to find the relevant function:
$kwin/libinput/connection.cpp:applyScreenToDevice
Looks like there is no si
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #2 from lo...@kde.bt.alestan.publicvm.com ---
(In reply to Vlad Zahorodnii from comment #1)
> Are you on X11 or Wayland?
Wayland.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411877
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #1 from Vlad Zahorodnii ---
Are you on X11 or Wayland?
--
You are receiving this mail because:
You are watching all bug changes.
29 matches
Mail list logo
