https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #29 from Till Schäfer ---
(In reply to Andrey from comment #28)
> Err, sorry I didn't think of that VMs are just (X?)Wayland apps also, so the
> tests should depend on environment you test them on..
> Any chance to test on real HW?
Well
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #28 from Andrey ---
Err, sorry I didn't think of that VMs are just (X?)Wayland apps also, so the
tests should depend on environment you test them on..
Any chance to test on real HW?
Anyway, I'll test that VMs also, thanks.
--
You are
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #27 from Till Schäfer ---
(In reply to Andrey from comment #26)
> We still need a way to reproduce it on unaffected distros (if any).
> Could you try to reproduce on VM?
Tested the following images inside a VM.
neon-testing-20211102-1850
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #26 from Andrey ---
We still need a way to reproduce it on unaffected distros (if any).
Could you try to reproduce on VM?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444589
Till Schäfer changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #24 from Till Schäfer ---
(In reply to Till Schäfer from comment #23)
> (In reply to Andrey from comment #21)
> > What else comes to mind is different libinput library versions maybe..
> >
> > Anyway, from Elisa's flatpak manifest you can
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #23 from Till Schäfer ---
(In reply to Andrey from comment #21)
> What else comes to mind is different libinput library versions maybe..
>
> Anyway, from Elisa's flatpak manifest you can dig out every component
> version of properly
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #22 from Till Schäfer ---
(In reply to Andrey from comment #20)
> Could you check with KDE's patched Qt, installing it manually instead or
> trying distros already shipped one?
> https://community.kde.org/Qt5PatchCollection
For my main
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #21 from Andrey ---
What else comes to mind is different libinput library versions maybe..
Anyway, from Elisa's flatpak manifest you can dig out every component version
of properly working build:
https://bugs.kde.org/show_bug.cgi?id=444589
Andrey changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #19 from Andrey ---
(In reply to Till Schäfer from comment #17)
> I was wondering if
> flatpak is tampering with something of the graphics or input stack. like
> vsync or so.
>From system POV it's just usual app but sandboxed. It speaks
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #18 from Andrey ---
Still it might be a regression, so it's worth to test it maybe in VM with Neon
(but not sure if such kind of test is correct on VMs).
You could test first your distro on VM to make sure the issue happens there,
then test
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #17 from Till Schäfer ---
(In reply to Andrey from comment #16)
> (In reply to Till Schäfer from comment #15)
> > I was wondering why qt 5.15.3 is used since this version is non-free. Maybe
> > there is a qt fix upstream available?
> Where
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #16 from Andrey ---
(In reply to Till Schäfer from comment #15)
> I was wondering why qt 5.15.3 is used since this version is non-free. Maybe
> there is a qt fix upstream available?
Where do you see this info?
It uses org.kde.Platform
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #15 from Till Schäfer ---
(In reply to Andrey from comment #14)
> Could you test Flathub version? It should be better chances we get similar
> results:
> https://flathub.org/apps/details/org.kde.elisa
Hmm, the flatpack version does not
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #14 from Andrey ---
Could you test Flathub version? It should be better chances we get similar
results:
https://flathub.org/apps/details/org.kde.elisa
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #13 from Till Schäfer ---
(In reply to Till Schäfer from comment #12)
> I can reproduce the issue with fedoras live image (version 34-1.2)
> installing the package elisa-player.
>
> The settings page does not really give you a precise
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #12 from Till Schäfer ---
I can reproduce the issue with fedoras live image (version 34-1.2) installing
the package elisa-player.
The settings page does not really give you a precise indication on how fast it
is, but I got about 4300
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #11 from Andrey ---
(In reply to Till Schäfer from comment #3)
> Elisa (search albums) -> affected
I tested on Gnome Wayland and didn't find any difference in max rates between
Elisa and Terminal there. It's about 1000 per sec in both
https://bugs.kde.org/show_bug.cgi?id=444589
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #10 from Andrey ---
Can you test on other compositors/desktops?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #9 from Till Schäfer ---
Thus, this might become a problem for low performance computers (mine is quite
ok).
Operating System: Gentoo Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version:
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #8 from Till Schäfer ---
With a system under stress and "Force lowest latency" setting, i can bring my
system down to a repeat rate of about 20 repeats/s
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444589
--- Comment #7 from Till Schäfer ---
There is another hint, that rendering / compositor is involved. When I select
Latency "Force lowest latency (may cause dropped frames)" under systemsettings
-> Compositor, the maximum repeat rate caps at about 30
https://bugs.kde.org/show_bug.cgi?id=444589
Till Schäfer changed:
What|Removed |Added
Summary|[libinput] [wayland]|[libinput] [wayland]
25 matches
Mail list logo