https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #4 from Antonio Orefice ---
Today i decided to go the kde way to see if could improve the situation, but
failed.
I installed colord-kde, loaded custom icc profiles, applied it, then i tried
to:
* Change resolution via kde screen kcm
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #5 from Antonio Orefice ---
If anybody needs it, this seems like a good workaround till things will be
sorted out:
#!/bin/bash
dbus-monitor --profile "type='signal',sender='org.kde.KWin',path=/ColorCorrect"
https://bugs.kde.org/show_bug.cgi?id=435423
Bug ID: 435423
Summary: Morphing popups effect does not morph. (no X-Fade)
Product: kwin
Version: 5.21.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: nor
https://bugs.kde.org/show_bug.cgi?id=435423
--- Comment #2 from Antonio Orefice ---
Hi, i tested woth same results on intel haswell and intel ivybridge.
Maximize effect does x-fades.
Do you think is an hardware/driver issue?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=214547
--- Comment #41 from Antonio Orefice ---
yakuake 20.12.3 opens new tabs in the same directories of the old one.
Is this bug still valid?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435423
--- Comment #3 from Antonio Orefice ---
Meantime, i removed the "CrossFadePrevious" part from the morphingpopup.js:
if (!couldRetarget) {
window.fadeAnimation = animate({
window: window,
https://bugs.kde.org/show_bug.cgi?id=439689
Antonio Orefice changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #15 from Antonio Orefice ---
Maybe related, or not, we lost xfade on window resize too when using the resize
effect that scales the window texture.
I managed to bring xfade for (un)maximize effect by downgrading
kwin,kdecoration and
https://bugs.kde.org/show_bug.cgi?id=424825
--- Comment #6 from Antonio Orefice ---
21.08.2 is still affected
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435423
--- Comment #6 from Antonio Orefice ---
Used to work with some glitches in plasma 5.22.5 due to this being fixed:
https://bugs.kde.org/show_bug.cgi?id=439689
Now the same bug has returned and this is following.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #16 from Antonio Orefice ---
f432ba78 | GOOD
ebc785167 | BAD
I'm unable to build in between, sorry.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438874
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #8 from Antonio Orefice ---
Thank you for opening the bug report, i was just going to fill one myself.
Confirmed of me, of course.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439689
Bug ID: 439689
Summary: Crossfade window effect does not work
Product: kwin
Version: 5.22.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=439689
Antonio Orefice changed:
What|Removed |Added
Summary|Crossfade window effect |Maximize effect: no more
https://bugs.kde.org/show_bug.cgi?id=438079
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=438079
Antonio Orefice changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=438478
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=430521
Antonio Orefice changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #27 from Antonio Orefice ---
I've no lines beginning with "Window-Maximized", but i've just this:
"HDMI1 HDMI2 Window-Maximized 800x600=true"
Deleted, killed dolphin, but the problem persisted.
--
You are re
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #29 from Antonio Orefice ---
Hi Nate, i've attached one in the past in the other bug report:
https://bugs.kde.org/show_bug.cgi?id=434825
https://bugs.kde.org/attachment.cgi?id=137023
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #30 from Antonio Orefice ---
Created attachment 140348
--> https://bugs.kde.org/attachment.cgi?id=140348&action=edit
dolphinrc
(In reply to Antonio Orefice from comment #29)
> Hi Nate, i've attached one in the past i
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #31 from Antonio Orefice ---
Sorry for the confusion,
I've to retract my observations in comment 25 about ~/.config/dolphinrc, (i
read and spoke about dolphinui.rc, ,sorry)
Removing ~/.config/dolphinrc, does not change a thing.
Sorr
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #32 from Antonio Orefice ---
Created attachment 140350
--> https://bugs.kde.org/attachment.cgi?id=140350&action=edit
other resize problems when in dual panel mode
I've found that even using standard/shipped config files, ther
https://bugs.kde.org/show_bug.cgi?id=430521
Antonio Orefice changed:
What|Removed |Added
Status|NEEDSINFO |REOPENED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #35 from Antonio Orefice ---
Unfortunately on single screen setup (another system) things do not change.
About the other thing i reported, i think they are related in the way that
"dolphin is unable to correctly resize internal wi
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #36 from Antonio Orefice ---
(In reply to Nate Graham from comment #34)
> Thanks for the config file. I still cannot reproduce the issue even when I
> use it on my own Dolphin. :(
Given the config files posted, a way (not the only w
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #37 from Antonio Orefice ---
I bisected the issue, but even if i found the "bad" commit,
it is not much useful, because it just exposes a bug introduced earlier and i
cannot determine when using git bisect:
In the past, the lo
https://bugs.kde.org/show_bug.cgi?id=440382
Bug ID: 440382
Summary: Main toolbar elements messed up on (un)maximize then
using split view.
Product: dolphin
Version: 21.07.80
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=440382
Antonio Orefice changed:
What|Removed |Added
Summary|Main toolbar elements |Main toolbar elements
https://bugs.kde.org/show_bug.cgi?id=434825
Antonio Orefice changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #40 from Antonio Orefice ---
*** Bug 434825 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440382
Antonio Orefice changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #41 from Antonio Orefice ---
*** Bug 440382 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #2 from Antonio Orefice ---
Created attachment 140468
--> https://bugs.kde.org/attachment.cgi?id=140468&action=edit
maximize/minimize, no crossfade video.
Oh weird, it is broken on 3 systems here.
Fun fact:
the first morphing t
https://bugs.kde.org/show_bug.cgi?id=439689
Antonio Orefice changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=439689
Antonio Orefice changed:
What|Removed |Added
Version|5.22.3 |5.21.90
--- Comment #5 from Antonio Orefice
https://bugs.kde.org/show_bug.cgi?id=438458
Antonio Orefice changed:
What|Removed |Added
Product|yakuake |kwin
Component|general
https://bugs.kde.org/show_bug.cgi?id=438458
--- Comment #8 from Antonio Orefice ---
Works fine till kwin 5.21.90
Downgrading it makes it work (have to downgrade kwayland-server to the same
version too to make it happy)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435378
Antonio Orefice changed:
What|Removed |Added
Version|unspecified |5.21.90
Component|compositing
https://bugs.kde.org/show_bug.cgi?id=435378
--- Comment #3 from Antonio Orefice ---
Since downgrading kwin to the now reported version solves the issue, i think
the problem lies there.
This: https://bugs.kde.org/show_bug.cgi?id=438458
seems to be a dupe.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=438458
--- Comment #9 from Antonio Orefice ---
Bisected. The offending commit is:
koko@Gozer# git bisect good
47113e09b8a80497463725a795728a34e9db940c is the first bad commit
commit 47113e09b8a80497463725a795728a34e9db940c
Author: Vlad Zahorodnii
Date
https://bugs.kde.org/show_bug.cgi?id=435378
--- Comment #4 from Antonio Orefice ---
Bisected. The offending commit is:
koko@Gozer# git bisect good
47113e09b8a80497463725a795728a34e9db940c is the first bad commit
commit 47113e09b8a80497463725a795728a34e9db940c
Author: Vlad Zahorodnii
Date
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #6 from Antonio Orefice ---
Bisected. The offending commit is:
koko@Gozer# git bisect good
47113e09b8a80497463725a795728a34e9db940c is the first bad commit
commit 47113e09b8a80497463725a795728a34e9db940c
Author: Vlad Zahorodnii
Date
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #9 from Antonio Orefice ---
Thank YOU very much for your efforts.
However, the same commit affects: https://bugs.kde.org/show_bug.cgi?id=438458
which, by gut feeling, it should not be due to previous pixmap.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=434829
Antonio Orefice changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=434829
Antonio Orefice changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #14 from Antonio Orefice ---
Ok, can plasma just stop resetting the lut when resolution changes?
I've edited the bug title to reflect that.
If even that is not possible, feel free to close.
Have a good day.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #15 from Antonio Orefice ---
(In reply to Zamundaaa from comment #12)
> KWin does not have any information about what other applications are doing
> or not doing with the lut, so it can't keep your use case working.
In case you
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #17 from Antonio Orefice ---
Ok, I'm just going to use xrandr and trigger a lut reload.
If anyone needs:
koko@Gozer# cat /koko/scripts/benq.keep.lut.sh
#!/bin/bash
dispwin -d 1 -s /koko/tmp/1.lut
dispwin -d 2 -s /koko/tmp/
https://bugs.kde.org/show_bug.cgi?id=467283
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=437844
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=437844
--- Comment #3 from Antonio Orefice ---
So I think there is something to be made about resource consumption.
As said, one core goes to 100% while it animates.
And when it is not enough, tipically while the view is complex with big icons,
active
https://bugs.kde.org/show_bug.cgi?id=437844
--- Comment #5 from Antonio Orefice ---
Nate, trying to fix this would mean a complete reimplementation of the
animation, because by now it seems that the splitter is just moved causing
continue repaints, rearrangments, system stress and of course it
https://bugs.kde.org/show_bug.cgi?id=438458
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438712
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438712
--- Comment #1 from Antonio Orefice ---
Happens here too.
Thanks for reporting, i was going to make the video myself.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438712
--- Comment #2 from Antonio Orefice ---
Ah, i forgot to say that if you press "esc" to close the dialog, it don't
flashes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #18 from Antonio Orefice ---
Made a new video with updated dolphin ans same results as the already reported
bug you can still read about there: https://bugs.kde.org/show_bug.cgi?id=434825
The new video is available at:
https
https://bugs.kde.org/show_bug.cgi?id=434825
Antonio Orefice changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #19 from Antonio Orefice ---
*** Bug 434825 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430521
Antonio Orefice changed:
What|Removed |Added
Status|NEEDSINFO |REOPENED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=437289
Bug ID: 437289
Summary: Oxygen plasma style: unreadable white text on white
background
Product: plasmashell
Version: 5.21.5
Platform: Other
OS: Linux
S
https://bugs.kde.org/show_bug.cgi?id=437289
--- Comment #1 from Antonio Orefice ---
It seems that some plasma elements
obey to:
[Colors:View]
BackgroundNormal
But Ignores:
[Colors:View]
ForegroundNormal
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435423
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=435423
--- Comment #5 from Antonio Orefice ---
Created attachment 140545
--> https://bugs.kde.org/attachment.cgi?id=140545&action=edit
Full morphingpopup.js that discards crossfades when the previous texture is
wrong or missing.
Full morphingpopup.
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #21 from Antonio Orefice ---
(In reply to MikeC from comment #18)
> I wonder if this is related: https://github.com/indilib/indi/pull/1521
I don't think so...
If you open removable devices from systemsettings5, you can still see
https://bugs.kde.org/show_bug.cgi?id=424825
Antonio Orefice changed:
What|Removed |Added
Resolution|DUPLICATE |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=424825
Antonio Orefice changed:
What|Removed |Added
Summary|yakuake 20.04.3 wont go |yakuake wont go fullscreen
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #35 from Antonio Orefice ---
(In reply to Attila from comment #34)
> Here is my workaround until this bug has been fixed.
> You need two USB devices. Let's call the first one "a dummy USB device".
>
> 1. Just P
https://bugs.kde.org/show_bug.cgi?id=442129
Bug ID: 442129
Summary: Window resize effect: some apps becomes transparents
for a while.
Product: kwin
Version: 5.22.3
Platform: Other
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=442129
--- Comment #1 from Antonio Orefice ---
Created attachment 141362
--> https://bugs.kde.org/attachment.cgi?id=141362&action=edit
resize konsole and dolphin
forgot the attachment
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #38 from Antonio Orefice ---
(In reply to Joshua T from comment #37)
> I just tried Fedora KDE Rawhide with Wayland, and I didn't have any issues
> on my Intel UHD 600. Animations were very close to 60 FPS. I have definitely
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #42 from Antonio Orefice ---
(In reply to Joshua T from comment #40)
> (In reply to Antonio Orefice from comment #38)
> > (In reply to Joshua T from comment #37)
> > > I just tried Fedora KDE Rawhide with Wayland, and
https://bugs.kde.org/show_bug.cgi?id=462164
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #47 from Antonio Orefice ---
(In reply to Lemmiwinks from comment #46)
> I think I made an observation: under System Settings -> Compositor, setting
> the latency to "force smoothest animations", seems to almost fix t
https://bugs.kde.org/show_bug.cgi?id=364766
--- Comment #46 from Antonio Orefice ---
Building qt is not an option for me, i'm sorry.
However i'm using GraphicsResetNotifications on qt 5.11.1 since a couple of
months and have had 2 or 3 freezes at most, so it would not be easy to d
https://bugs.kde.org/show_bug.cgi?id=299306
Antonio Orefice changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=393422
Bug ID: 393422
Summary: Launch feedback (even static cursor) needs opengl
compositor running (X11)
Product: plasmashell
Version: 5.12.4
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=393422
--- Comment #2 from Antonio Orefice ---
kinda "understood", thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=355935
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #58 from
https://bugs.kde.org/show_bug.cgi?id=355935
--- Comment #62 from Antonio Orefice ---
At least for folderviews, i noticed that it happens only when the text is
"center aligned" (task manager looks good), so here comes my hacky workaround
for plasmashell.
in
/usr/share/plasma
https://bugs.kde.org/show_bug.cgi?id=355935
--- Comment #63 from Antonio Orefice ---
I noticed another interesting behaviour.
When kerning looks bad, if i open font configuration and change anything
related to the font used for the desktop (General font), it looks nice.
I mean, not only changing
https://bugs.kde.org/show_bug.cgi?id=393568
Bug ID: 393568
Summary: Logout screen opacity is too low
Product: plasmashell
Version: 5.12.4
Platform: Archlinux Packages
OS: All
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=393568
--- Comment #1 from Antonio Orefice ---
Created attachment 112284
--> https://bugs.kde.org/attachment.cgi?id=112284&action=edit
logout screen on bright background
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=332512
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #74 from
https://bugs.kde.org/show_bug.cgi?id=353983
--- Comment #138 from Antonio Orefice ---
I don't understand; the case specific to the issue this bug is reporting
(Turning off compositing breaks Plasma panel rendering) is fixed?
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #35 from Antonio Orefice ---
I repeat, the bug i reported (this one) was not about wallpaper/images photo
widgets and so on.
if the underlying cause is the same, i don't know.
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #39 from Antonio Orefice ---
Me, the OP,
reported the issue on QT 5.7.x times, so the bug here:
https://bugreports.qt.io/browse/QTBUG-61754 does not apply at all.
Is there any chance to bring the title of this back to the original, the
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #45 from Antonio Orefice ---
qt5 5.10.0 here.
Memory increases over time as described in the first post, nothing changed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #53 from Antonio Orefice ---
QSG_RENDER_LOOP makes no difference to me (i'm not testing media frame widgets
or slideshow wallpaper, see first post).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #59 from Antonio Orefice ---
I'm glad you guys found a workaround for your particular case.
However, mine (see first post), is still present.
I just made a video showing how plasma can reach about 1GB of ram usage from
300MB in a bun
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #61 from Antonio Orefice ---
Exactly.
Exactly what i reported when i opened this bug, see comment #1.
I don't want to be harsh, but this 'bug report' is becoming a mess since it has
been arbitrarily joined/defaced with some
https://bugs.kde.org/show_bug.cgi?id=391507
Bug ID: 391507
Summary: Ugly rendering of notification pictures
(Nearest-neighbor)
Product: plasmashell
Version: 5.12.2
Platform: Other
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=391507
--- Comment #3 from Antonio Orefice ---
plasma-framework is 5.43.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370953
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=394436
Bug ID: 394436
Summary: Serius memory leak when realigning folderview widget
icons.
Product: plasmashell
Version: 5.12.5
Platform: Other
OS: Linux
Stat
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #122 from Antonio Orefice ---
So, i open another one, it is simpler.
Could you guys please test? It is a plasma js script that will use all of my
memory just re-aligning folderview icons over and over
Here:
https://bugs.kde.org/show_bug.cgi
https://bugs.kde.org/show_bug.cgi?id=394436
Antonio Orefice changed:
What|Removed |Added
Summary|Serius memory leak when |Serious memory leak when
https://bugs.kde.org/show_bug.cgi?id=394436
Antonio Orefice changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
201 - 300 of 415 matches
Mail list logo
