https://bugs.kde.org/show_bug.cgi?id=328987
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=468346
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=468346
Bug ID: 468346
Summary: Invalid .desktop files can crash plasmashell when
trying to edit them from kickoff.
Classification: Plasma
Product: plasmashell
Version: 5.27.4
https://bugs.kde.org/show_bug.cgi?id=460260
David Rubio changed:
What|Removed |Added
Platform|Fedora RPMs |Archlinux
--- Comment #10 from David Rubio
https://bugs.kde.org/show_bug.cgi?id=460260
David Rubio changed:
What|Removed |Added
Keywords||multiscreen, usability
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=460260
--- Comment #2 from David Rubio ---
I want to add that this mostly happens with KDE apps. It works for GTK apps,
for example.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460260
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=427875
--- Comment #84 from David Rubio ---
(In reply to Nate Graham from comment #83)
> Not to my knowledge; let's get a new one going. Can you make sure to write
> detailed steps to reproduce in it? Thanks!
I filed it on 460260. Let me know if yo
https://bugs.kde.org/show_bug.cgi?id=460260
Bug ID: 460260
Summary: On a multi screen setup on Wayland, KDE app windows do
not remember the size they had if the primary monitor
is not the leftmost one.
Classification: Frameworks
https://bugs.kde.org/show_bug.cgi?id=460223
--- Comment #1 from David Rubio ---
Adding that IntelliJ runs as a X11 application. I do not run any X11
applications beside this one (java please add Wayland support...), so I'm not
too sure if anything could be going on here. I tried running another
https://bugs.kde.org/show_bug.cgi?id=460223
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=460223
Bug ID: 460223
Summary: Closing IntelliJ IDEA 2022.2.3 crashes kwin_wayland
completely
Classification: Plasma
Product: kwin
Version: 5.25.5
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=427875
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=431959
--- Comment #2 from David Rubio ---
Going back to KDE Frameworks 5.78 and kscreenlocker 5.20.80 fixes the issue.
Since 5.79 is really early work, it's probably a fluke more than anything, but
just putting this one the table for clarification.
--
You
https://bugs.kde.org/show_bug.cgi?id=432477
--- Comment #7 from David Rubio ---
(In reply to Michail Vourlakos from comment #6)
> Definitely a PlasmaCore.IconItem issue... I moved the Tasks codepage to
> Kirigami.Icon(s) and everything is painted correctly in my system.
Yup, it's fi
https://bugs.kde.org/show_bug.cgi?id=432477
--- Comment #4 from David Rubio ---
(In reply to Michail Vourlakos from comment #3)
> You can try the latest commit, it is trying to workaround and make things a
> bit more affordable. It is trying to be crispy for normal size and smooth
> i
https://bugs.kde.org/show_bug.cgi?id=432477
--- Comment #2 from David Rubio ---
With "icon zoom" on hover, it seems to pretty much go away, but the animation
is super jaggy.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432477
--- Comment #1 from David Rubio ---
Icon being hovered: https://i.imgur.com/mstlJef.png
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432477
Bug ID: 432477
Summary: [git version] Jaggy icons when hovering over them (or
not)
Product: lattedock
Version: git (master)
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=432444
--- Comment #6 from David Rubio ---
(In reply to Michail Vourlakos from comment #5)
> yeah open it...
> and we can forward it to Plasma afterwards. Latte is now using
> PlasmaCore.IconItems in roundToIconSize:false state so Latte can not fix
&
https://bugs.kde.org/show_bug.cgi?id=432444
--- Comment #4 from David Rubio ---
(In reply to Michail Vourlakos from comment #3)
> please try again, it should be fixed now. The should look crispy when the
> tasks an not hovered and when a task is fully zoomed through the parabolic
> effe
https://bugs.kde.org/show_bug.cgi?id=432444
--- Comment #1 from David Rubio ---
On d46864e0ade1f0edee7a6bc4b9f6a219baea79aa setting the dock size to 47x or 46x
(or 49x) still results in a midly-sharp icon. On latest git it's definitely way
way blurrier.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=432444
Bug ID: 432444
Summary: Blurry icons on latte tasks (on latest -git)
Product: lattedock
Version: git (master)
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=431959
--- Comment #1 from David Rubio ---
Created attachment 135073
--> https://bugs.kde.org/attachment.cgi?id=135073=edit
/usr/lib/libexec/kscreenlocker_greet --testing logs
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431959
Bug ID: 431959
Summary: Can't unlock screen using KScreenLocker at all --
Password is always incorrect.
Product: kscreenlocker
Version: unspecified
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=428613
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=431643
--- Comment #5 from David Rubio ---
(In reply to David Edmundson from comment #4)
> From the hotspot it appears the FrameSVGItem is the worst offender of those
> two issues.
>
> Copying some context from the other report.
>
> * F
https://bugs.kde.org/show_bug.cgi?id=430524
--- Comment #6 from David Rubio ---
As a small heads-up, this also happens to kscreenlocker. If I have my mouse
focused on screen A, the password * chars will start to be shown on screen B.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=424795
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=431643
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=417716
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #31 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #30)
> (In reply to David Rubio from comment #27)
> > It fixes it for me. Also the maximize animation is way smoother for some
> > weird reason.
&g
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #28 from David Rubio ---
(In reply to David Edmundson from comment #24)
> Turns out the center is still visible slightly in the top. We can't just
> disable it.
>
> It's fixable with a oneline in the theme, adding an element
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #27 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #26)
> @David Rubio Can you please check whether 2d1994e0669 made things better?
It fixes it for me. Also the maximize animation is way smoother for some weird
rea
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #18 from David Rubio ---
Created attachment 134863
--> https://bugs.kde.org/attachment.cgi?id=134863=edit
kwinrc
(In reply to Vlad Zahorodnii from comment #17)
> > setting it to the slowest animation speed notch still plays
&g
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #16 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #15)
> On my machine, the maximize animation is choppy no matter where I click.
The animation is definitely choppy even when double-clicking. When I click the
maxim
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #14 from David Rubio ---
I find it really weird that the animation works only if I double click the
titlebar, but clicking the maximize button does absolutely nothing.
I tried reverting the cubic animation curve and that didn't do
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #12 from David Rubio ---
(In reply to David Rubio from comment #11)
> (In reply to Vlad Zahorodnii from comment #9)
> > The problem is that aurorae decoration engine is inefficient. KWin gets the
> > data from a textur
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #11 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #9)
> The problem is that aurorae decoration engine is inefficient. KWin gets the
> data from a texture where Aurorae composites the decoration and uploads it
> t
https://bugs.kde.org/show_bug.cgi?id=431509
--- Comment #42 from David Rubio ---
Definitely too late to comment, but the patch mentioned fixed it for me too.
It's super smooth now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431509
--- Comment #34 from David Rubio ---
Created attachment 134855
--> https://bugs.kde.org/attachment.cgi?id=134855=edit
Last one was wrong, this one is the actual file.
Oops. Sorry.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=431509
--- Comment #33 from David Rubio ---
Created attachment 134854
--> https://bugs.kde.org/attachment.cgi?id=134854=edit
Attaching KWin timestamp log.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431509
--- Comment #32 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #23)
> Created attachment 134845 [details]
> patch
>
> No, there is not. Now I wonder what presentation timestamps kwin receives
> via swap events.
&
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #14 from David Rubio ---
Though, after changing what I told you, VSync is still absolutely wrong on
XWayland apps: https://i.imgur.com/df82B3i.png
And Chromium running natively on Wayland isn't any better:
https://i.imgur.com/chVQSBR.png
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #13 from David Rubio ---
(In reply to David Rubio from comment #12)
> Oh wow. This is super cursed. I tried changing the common denominator
> between my laptop and my desktop: the kernel.
>
> Turns out on my desktop I h
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #12 from David Rubio ---
Oh wow. This is super cursed. I tried changing the common denominator between
my laptop and my desktop: the kernel.
Turns out on my desktop I have a kernel optimized for gaming (say, linux-tkg).
Well, turns out
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #11 from David Rubio ---
Nevermind. I started playing a video on Youtube and the stutter on Wayland is
back full throttle even on those commit hashes. X11 seems... fine, somehow.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #8 from David Rubio ---
Reverting:
kwayland-server: f67daa0711584058a8fefda76e898fe58d53ace7
kwin: 26b249061ee49dacc29320f93984de3d35012e1f
to those commit hashes makes this issue dissapear.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #10 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #9)
> Can you test kwayland-server and kwin at the following commits
>
> kwayland-server: f67daa0711584058a8fefda76e898fe58d53ac
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #8 from David Rubio ---
After a while of testing and a good minute or two of moving windows, I managed
to record it happening on X11 aswell, where there's only one RenderLoop:
https://youtu.be/GOkB5Wjx8Ac
It's way more rare on X11
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #7 from David Rubio ---
I tried removing my kwinrc just in case. It didn't make a difference either,
just in case.
Without a kwinrc the Wayland session took a whole 2 minutes to start. That
might be worth another bug report.
--
You
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #6 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #5)
> I wonder if it has anything to do with per-screen rendering. If there is
> only one monitor connected, does the screen still occasionally freeze?
Just
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #4 from David Rubio ---
Also KDE Frameworks version should be 5.79, oops. Dunno if anyone can edit
*that* part.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #3 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #2)
> Odd... Does kwin/wayland 5.20.x suffer from this issue as well or is it a
> regression?
5.20.5 is completely fine.
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=431546
David Rubio changed:
What|Removed |Added
OS|Other |Linux
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=431546
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=431546
--- Comment #1 from David Rubio ---
For additional info, my specs are as follows:
Ryzen 5 2600, RX 480, 16GB of RAM
My laptop, where this doesn't happen (for some reason) it's
Ryzen 5 3500U, Vega 8, 16GB of RAM
I have both a 144Hz and 60Hz monitor
https://bugs.kde.org/show_bug.cgi?id=431546
Bug ID: 431546
Summary: Stutter on Wayland session
Product: kwin
Version: git master
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=431509
--- Comment #12 from David Rubio ---
Video of the issue: https://youtu.be/5L_kVV2JGPU
Keep in mind this does happen on X11, but it's both not as incredibly bad, and
it doesn't pause your mouse movement or stop rendering what you're typing,
which
https://bugs.kde.org/show_bug.cgi?id=431509
--- Comment #11 from David Rubio ---
(In reply to David Rubio from comment #9)
> Okay, I tried "force smoothest animations" and I still saw lag. So I ran
> VSync tester and... I'm not crazy, everything is stuttering a LOT.
>
> I
https://bugs.kde.org/show_bug.cgi?id=431509
--- Comment #10 from David Rubio ---
(In reply to David Rubio from comment #9)
> Okay, I tried "force smoothest animations" and I still saw lag. So I ran
> VSync tester and... I'm not crazy, everything is stuttering a LOT.
>
> I
https://bugs.kde.org/show_bug.cgi?id=431509
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=431449
--- Comment #14 from David Rubio ---
(In reply to tempel.julian from comment #11)
> The difference between "Balance of latency and smoothness" and "prefer
> smoother animations" seems at least to be less with 125Hz mouse
https://bugs.kde.org/show_bug.cgi?id=431449
--- Comment #12 from David Rubio ---
431509 might also just be this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431449
--- Comment #13 from David Rubio ---
(In reply to David Rubio from comment #12)
> 431509 might also just be this.
At least in part, but it seems like it's not as cut clear and might be
different :p
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=431449
--- Comment #9 from David Rubio ---
Ah, if I move it slowly the Hz goes down. (In reply to David Rubio from comment
#8)
> evhz:
> Logitech G203 Prodigy Gaming Mouse: Latest 1000Hz, Average 906Hz
> Logitech G203 Prodigy Gaming Mouse: Lates
https://bugs.kde.org/show_bug.cgi?id=431449
--- Comment #8 from David Rubio ---
evhz:
Logitech G203 Prodigy Gaming Mouse: Latest 1000Hz, Average 906Hz
Logitech G203 Prodigy Gaming Mouse: Latest 500Hz, Average 898Hz
Logitech G203 Prodigy Gaming Mouse: Latest 500Hz, Average 890Hz
https://bugs.kde.org/show_bug.cgi?id=431450
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=431449
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=430524
--- Comment #5 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #4)
> Kickoff and KRunner position themselves. If they do it wrong, it's a
> plasmashell bug.
>
> As for osu! and Firefox, they most likely position themselve
https://bugs.kde.org/show_bug.cgi?id=431441
--- Comment #1 from David Rubio ---
I *thought* it might have been because I had keep thumbnails to always, but I
set it to Never to test, and I can get the same result even like so.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #7 from David Rubio ---
(In reply to David Rubio from comment #5)
> (In reply to Vlad Zahorodnii from comment #4)
> > Cannot reproduce.
> >
> > I wonder if kwin has a huge frame drop. Can you reduce the animation sp
https://bugs.kde.org/show_bug.cgi?id=431441
Bug ID: 431441
Summary: Minimizing some fullscreen windows causes the screen
to appear frozen
Product: kwin
Version: git master
Platform: Archlinux Packages
OS:
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #6 from David Rubio ---
Also for CSD windows it also plays 100% of the times. It's only when the window
is decorated by Aurorae.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #5 from David Rubio ---
(In reply to Vlad Zahorodnii from comment #4)
> Cannot reproduce.
>
> I wonder if kwin has a huge frame drop. Can you reduce the animation speed
> in the system settings?
I tried the minimum speed and
https://bugs.kde.org/show_bug.cgi?id=430524
--- Comment #3 from David Rubio ---
The game osu! also always opens in the wrong monitor, aka any monitor where the
cursor is *not* located at.
Firefox too, sometimes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431415
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #3 from David Rubio ---
If you try to replicate this issue, this *might* work sometimes, then out of
nowhere the effect will stop playing completely, then start again. Try using
your computer for 10 minutes or so with an Aurorae theme
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #2 from David Rubio ---
Video of the issue: https://www.youtube.com/watch?v=HS4vYuRlL1I
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431415
--- Comment #1 from David Rubio ---
Created attachment 134725
--> https://bugs.kde.org/attachment.cgi?id=134725=edit
qdbus org.kde.KWin /KWin supportInformation
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431415
Bug ID: 431415
Summary: Maximize animation does not work on Wayland
Product: kwin
Version: git master
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=430524
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=430524
--- Comment #2 from David Rubio ---
OBSERVED RESULT
KRunner and other windows (kickoff, for example) open on the monitor where the
mouse is NOT at.
Sorry, I filed the bug at 4AM, and the observed result should say that ;w;
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=430524
--- Comment #1 from David Rubio ---
Here's a video outlining the issue:
https://www.youtube.com/watch?v=Zgf5tCjAJqQ=youtu.be
Right now I'm running MR 507, *but* on KWin master without 507 applied, the
same thing happens. Same on KWin 5.20.4 directly
https://bugs.kde.org/show_bug.cgi?id=430524
Bug ID: 430524
Summary: Windows and Kickoff / KRunner opens in the wrong
monitor
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=400929
--- Comment #15 from David Rubio ---
(In reply to Albert Astals Cid from comment #14)
> (In reply to David Rubio from comment #12)
> > (In reply to David Rubio from comment #11)
> > > (In reply to Albert Astals Cid from comment #10)
&
https://bugs.kde.org/show_bug.cgi?id=400929
--- Comment #12 from David Rubio ---
(In reply to David Rubio from comment #11)
> (In reply to Albert Astals Cid from comment #10)
> > The patches are wrong, they change the behaviour of two things that are not
> > released in sync (k
https://bugs.kde.org/show_bug.cgi?id=400929
--- Comment #11 from David Rubio ---
(In reply to Albert Astals Cid from comment #10)
> The patches are wrong, they change the behaviour of two things that are not
> released in sync (kwalletd and pam-kwallet), so they would break every
> si
https://bugs.kde.org/show_bug.cgi?id=400929
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #70 from David Rubio ---
(In reply to David Rubio from comment #67)
> (In reply to Matthias Mueller from comment #66)
> > i only had a black wallpaper on the second monitor once since it was
> > "fixed". (Manjaro t
https://bugs.kde.org/show_bug.cgi?id=428379
David Rubio changed:
What|Removed |Added
CC||david.alejandro.rubio@gmail
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #67 from David Rubio ---
(In reply to Matthias Mueller from comment #66)
> i only had a black wallpaper on the second monitor once since it was
> "fixed". (Manjaro testing here, so currently qt5-base 5.15.1-3 and
> plas
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #65 from David Rubio ---
(In reply to d3coder from comment #63)
> For me it behaves like in 5.15.0, but randomly
> Panel is on wrong monitor, desktop icons are on wrong monitor, notifications
> appear near center of wrong monitor.
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #64 from David Rubio ---
Interesting. I can confirm is quite random now though. It happens like at
really random times and sometimes it stops happening for a while and then it
confuses me :p
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #62 from David Rubio ---
Well, actually, notifications now are in the correct monitor when it happens,
so is KRunner. The issue is only now with the wallpaper, which either:
- Goes black on second monitor
- Is shuffled between monitors
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #61 from David Rubio ---
same as d3coder
I could record another video, but its basically the same behavior.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #57 from David Rubio ---
I can confirm this is happening again. Started happening somewhere between
plasmashell 5.20.0 and 5.20.2, somehow :p
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #52 from David Rubio ---
Thanks you all for the help <3
I chimed in on Arch's bug tracker to backport the fix. Haven't heard back,
though.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426496
--- Comment #49 from David Rubio ---
(In reply to Daniel Baumgartner from comment #48)
> It's fixed with Qt 5.15.1-2.1 (opensuse tumbleweed 20200925)
>
> changelog:
> - Revert commit to fix screen geometry on startup (boo#1176750,
https://bugs.kde.org/show_bug.cgi?id=416497
--- Comment #7 from David Rubio ---
Probably more useful note, even: Deepin's fork of KWin has this bug fixed.
Maybe worth a look there?
--
You are receiving this mail because:
You are watching all bug changes.
1 - 100 of 136 matches
Mail list logo
