https://bugs.kde.org/show_bug.cgi?id=358472
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #34 from idmresettrial ---
I think I've solved the problem by switching the touchpad driver from synaptic
to libinput.
You can close the bug if you want.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358472
idmresettrial changed:
What|Removed |Added
Version|5.5.3 |5.13.0
Platform|Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=358472
idmresettrial changed:
What|Removed |Added
CC||idmresettr...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #32 from Nate Graham ---
Fantastic news!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #31 from akm ---
hi,
it just reached Tumbleweed it seems as I am on libQT 5.10.0-3 and issue is gone
as far as I can tell.
Thank you
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358472
David Edmundson changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #29 from akm ---
Hello Lorenzo
Am on Tumbleweed, it has xf86-input-evdev installed.
did a diff between the already installed /etc/X11/xorg.conf.d/10-evdev.conf and
yours and they are a 100% match.
So at least on
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #28 from Lorenzo Murarotto ---
Found a workaround (for arch linux):
1. Install xf86-input-evdev
2. Create file /etc/X11/xorg.conf.d/10-evdev.conf (Delete existing if needed).
3. Put https://pastebin.com/Y5cePdTj in said
https://bugs.kde.org/show_bug.cgi?id=358472
David Edmundson changed:
What|Removed |Added
CC||lnz...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=358472
Nate Graham changed:
What|Removed |Added
CC||pointedst...@zoho.com
--
https://bugs.kde.org/show_bug.cgi?id=358472
Dr. Chapatin changed:
What|Removed |Added
CC||yy...@gmx.com
--- Comment #26
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #24 from David Edmundson ---
Upstream bug report: https://bugreports.qt.io/browse/QTBUG-59261
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358472
David Edmundson changed:
What|Removed |Added
CC||andy...@mail.ru
https://bugs.kde.org/show_bug.cgi?id=358472
Alex Tucker changed:
What|Removed |Added
CC||a...@floop.org.uk
--
You are
https://bugs.kde.org/show_bug.cgi?id=358472
David Edmundson changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #22 from Matthias Dahl ---
(In reply to Dmitry Belyakin from comment #21)
> Could it be related to libinput?
The problem is with Qt -- and it has been located (= the commit that caused it
and why it is
https://bugs.kde.org/show_bug.cgi?id=358472
Dmitry Belyakin changed:
What|Removed |Added
CC||d-belya...@ya.ru
---
https://bugs.kde.org/show_bug.cgi?id=358472
Christoph Feck changed:
What|Removed |Added
CC||k...@web.de
--- Comment #20
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #19 from Ilya Bizyaev ---
For some reason, this bug is not present in Kubuntu although is has the same Qt
version.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #18 from akm ---
(In reply to Ilya Bizyaev from comment #17)
> Same problem here.
> Fresh install of openSUSE Leap 42.2.
see the link from Matthias: https://bugreports.qt.io/browse/QTBUG-55638
it needs to be fixed by
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #17 from Ilya Bizyaev ---
Same problem here.
Fresh install of openSUSE Leap 42.2.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358472
Ilya Bizyaev changed:
What|Removed |Added
CC||bizyaev.g...@yandex.ru
https://bugs.kde.org/show_bug.cgi?id=358472
Christian Stadelmann changed:
What|Removed |Added
URL|
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #15 from Matthias Dahl ---
(In reply to akm from comment #14)
> can also confirm this on Thumbleweed, took me a while to find this bug
> report, just glad its not only me getting irritated by it :)
Thanks for
https://bugs.kde.org/show_bug.cgi?id=358472
akm changed:
What|Removed |Added
CC||a.vank...@chello.nl
--- Comment #14
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #13 from Matthias Dahl ---
A quick grep revealed that apart from KWIN, a few other places still use
ScrollView and would need adaptation as well to set the Flickable's
pixelAligned=true to avoid the
https://bugs.kde.org/show_bug.cgi?id=358472
Kai Uwe Broulik changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #11 from Matthias Dahl ---
Like expected, this issue can be seen in other places as well. Pretty much
everywhere where something inherited from Flickable is issued, like the Widgets
browser (via "Add
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #10 from Matthias Dahl ---
Created attachment 100867
--> https://bugs.kde.org/attachment.cgi?id=100867=edit
severe corruption in kickoff
Here another example screenshot where the corruption was more
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #9 from Matthias Dahl ---
Since this also belongs here, I am copying and pasting from the Qt bug report
where I just added the following:
Ok, here what I have been able to debug:
Everything that uses
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #8 from Matthias Dahl ---
Like expected, a minimal Qt example was asked for in the Qt bug report.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #7 from Matthias Dahl ---
Meanwhile I have also tested this with a fresh OpenSuSE Tumbleweed Live iso in
a virtual machine and the issue is also 100% reproducible there as well.
I have also taken the liberty
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #6 from Matthias Dahl ---
I forgot to mention: I also tested this with Qt's 5.6 git branch as of today --
the corruption is absolutely the same, even though a lot of font and scrolling
related fixes went in
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #5 from Matthias Dahl ---
Created attachment 100847
--> https://bugs.kde.org/attachment.cgi?id=100847=edit
font corruption after one wheel unit in application launcher
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #4 from Matthias Dahl ---
Created attachment 100846
--> https://bugs.kde.org/attachment.cgi?id=100846=edit
font corruption after one wheel unit in kcm desktop effects
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #3 from Matthias Dahl ---
I can confirm this issue as well. It has been long-standing, unfortunately.
I will attach two more screenshots which show it rather prominently -- one from
the application launcher
https://bugs.kde.org/show_bug.cgi?id=358472
Matthias Dahl changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #1 from Christian Stadelmann ---
Created attachment 96810
--> https://bugs.kde.org/attachment.cgi?id=96810=edit
software updates widget with corrupted fonts
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=358472
--- Comment #2 from Christian Stadelmann ---
Created attachment 96811
--> https://bugs.kde.org/attachment.cgi?id=96811=edit
device manager with corrupted fonts
--
You are receiving this mail because:
You are watching all
40 matches
Mail list logo