https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #67 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #66)
> If you run latte through command prompt with, latte-dock -d
>
> Do you get something interesting especially when the issue appears?
no, not really, no info
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #66 from Michail Vourlakos ---
If you run latte through command prompt with, latte-dock -d
Do you get something interesting especially when the issue appears?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #65 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #64)
> (In reply to Alexandre Pereira from comment #63)
> >
> > It sucks that you cannot reproduce it, makes it really hard. If I can give
> > any more info in any
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #64 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #63)
>
> It sucks that you cannot reproduce it, makes it really hard. If I can give
> any more info in any way, just ask.
yeah, if you find something new report
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #63 from Alexandre Pereira ---
Did you had alot of pinned apps ? I noticed that if I "start clean" with no
pinned apps, cpu usage is nowhere near as normal. Readding them makes cpu usage
go again high.
Well, ok, if I am able to get more
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #62 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #61)
> btw, don't know if this is important:
>
> I was just testing with new latte-dock configs, and I noticed that if I
> praticly don't have any launchers pinned,
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #61 from Alexandre Pereira ---
btw, don't know if this is important:
I was just testing with new latte-dock configs, and I noticed that if I
praticly don't have any launchers pinned, it seems like it doesn't use alot of
cpu ( and no
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #60 from Alexandre Pereira ---
it does happen, with your kwin rules and script. So uploaded latte config
files.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #59 from Alexandre Pereira ---
Created attachment 117969
--> https://bugs.kde.org/attachment.cgi?id=117969=edit
latte config files
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #58 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #55)
> in what way ? the app changing its title ? or the kwin rules part ?
> if the app changing its title, i will search for an easier way
Let's try the following,
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #57 from Michail Vourlakos ---
Created attachment 117968
--> https://bugs.kde.org/attachment.cgi?id=117968=edit
bash script for konsole testing
bash script for konsole testing
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #56 from Michail Vourlakos ---
Created attachment 117967
--> https://bugs.kde.org/attachment.cgi?id=117967=edit
kwin rule for konsole
kwin rule for konsole
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #55 from Alexandre Pereira ---
in what way ? the app changing its title ? or the kwin rules part ?
if the app changing its title, i will search for an easier way
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #54 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #53)
> (In reply to Michail Vourlakos from comment #52)
> > (In reply to Alexandre Pereira from comment #51)
> Were you able to reproduce it in your machine ?
not
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #53 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #52)
> (In reply to Alexandre Pereira from comment #51)
> > Another workaround is to keep latte-dock and kwin rules as it is (using
> > title rules), but instead of
https://bugs.kde.org/show_bug.cgi?id=399149
Michail Vourlakos changed:
What|Removed |Added
Component|application |plasmoid
--- Comment #52 from Michail
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #51 from Alexandre Pereira ---
Another workaround is to keep latte-dock and kwin rules as it is (using title
rules), but instead of using latte-dock taskmanager, use a latte-dock panel and
then add the plasma icon taskmanager into it.
So,
https://bugs.kde.org/show_bug.cgi?id=399149
Michail Vourlakos changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #49 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #48)
> (In reply to Alexandre Pereira from comment #47)
> > I think I solved it ( I can be wrong, as the history of this bug report
> > shows )
> >
> > I think the
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #48 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #47)
> I think I solved it ( I can be wrong, as the history of this bug report
> shows )
>
> I think the latte-dock high cpu usage with when kwin is using a rule
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #47 from Alexandre Pereira ---
I think I solved it ( I can be wrong, as the history of this bug report shows )
I think the latte-dock high cpu usage with when kwin is using a rule that
compares the title.
So in the konsole test, i removed
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #46 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #45)
> (In reply to Alexandre Pereira from comment #44)
> > OK, more testing:
> >
> > setting update frequency to 5 seconds, latte-dock usage is almost none,
> >
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #45 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #44)
> OK, more testing:
>
> setting update frequency to 5 seconds, latte-dock usage is almost none,
> being at 0% most of the time and then from time to time ( i
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #44 from Alexandre Pereira ---
OK, more testing:
setting update frequency to 5 seconds, latte-dock usage is almost none, being
at 0% most of the time and then from time to time ( i guess 5 seconds ) a 2%
usage.
If you are having trouble
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #43 from Alexandre Pereira ---
Created attachment 117964
--> https://bugs.kde.org/attachment.cgi?id=117964=edit
kwin rule affecting konsole
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #42 from Alexandre Pereira ---
Finally, been doing more testing and am able to reproduce with konsole.
OK, so no need to open lots of konsole apps, only 1 or 2 will suffice ( i test
with 2 because I run sometimes 2 windows of the wine app
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #41 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #39)
> sorry, the command is correct, but only for fish shell.
>
> for bash its :
>
> qdbus $KONSOLE_DBUS_SERVICE $KONSOLE_DBUS_SESSION
>
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #40 from Alexandre Pereira ---
Also, sorry, in konsole, options for title be app name to be disabled ( or
else, the title will always be the app running )
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #39 from Alexandre Pereira ---
sorry, the command is correct, but only for fish shell.
for bash its :
qdbus $KONSOLE_DBUS_SERVICE $KONSOLE_DBUS_SESSION
org.kde.konsole.Session.setTitle 1 `date +%s%N`
what I do is create a date.sh with
#!
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #38 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #37)
> Unfortunatly i cannot hide the clock ( and whats even worse, the title has
> clock and network packets info ).
>
> I did a test, which some 6 konsole windows
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #37 from Alexandre Pereira ---
Unfortunatly i cannot hide the clock ( and whats even worse, the title has
clock and network packets info ).
I did a test, which some 6 konsole windows running "qdbus $KONSOLE_DBUS_SERVICE
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #36 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #35)
> Hi,
>
> Can you give some info as how and where it was resolved ?
>
> I still suffer from this problem :( Only workaround I found was using the
> app
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #35 from Alexandre Pereira ---
Hi,
Can you give some info as how and where it was resolved ?
I still suffer from this problem :( Only workaround I found was using the app
through explorer.exe virtual desktop, but its bad, wine's virtual
https://bugs.kde.org/show_bug.cgi?id=399149
Michail Vourlakos changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #34 from Alexandre Pereira ---
More info:
Seems the problem goes away with that checkbox because kwin stops detecting
that window.
More testing, shows that there is a problem with multiple rules for the same
app/window, starting 5.14.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #33 from Alexandre Pereira ---
Freaking nailed it, found out what was the problem
See video : https://drive.google.com/open?id=10Q9pNV959RyGSCbr6fh9WPJEQSXdQudC
Don't know why that started to be a problem. Those rules are actually from a
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #32 from Alexandre Pereira ---
ok, i understand, its a corner case that you can't even test in your system.
thanks for all the assistance ! if i find out something interesting I will let
you know.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=399149
Michail Vourlakos changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #30 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #29)
> (In reply to Alexandre Pereira from comment #28)
> > Ok, found out how to make latte-dock use less cpu: unpin all my latte-dock
> > pinned launchers.
> >
> >
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #29 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #28)
> Ok, found out how to make latte-dock use less cpu: unpin all my latte-dock
> pinned launchers.
>
> That made it almost use no cpu.
and now try to reproduce
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #28 from Alexandre Pereira ---
Ok, found out how to make latte-dock use less cpu: unpin all my latte-dock
pinned launchers.
That made it almost use no cpu.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #27 from Alexandre Pereira ---
I am doing more investigations on this.
Right now I have latte-dock using between 0%~1% cpu with 2 windows. most of the
time its at 0%. But its like this because I "rm -rf .config/latte*".
Restoring the
https://bugs.kde.org/show_bug.cgi?id=399149
Alexandre Pereira changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #25 from Alexandre Pereira ---
Also, more info:
I made a debug print on every function call of that file. only
windowChangedProxy was "spammed".
Also, I tested disabling (removing) the windowChangedProxy signal connect, so
its not called
https://bugs.kde.org/show_bug.cgi?id=399149
Alexandre Pereira changed:
What|Removed |Added
Resolution|FIXED |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=399149
Michail Vourlakos changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #22 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #20)
please can you test again master version and see if we fixed it or at least
that
emit windowChanged(wid);
is not triggered any more?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=399149
Michail Vourlakos changed:
What|Removed |Added
Version Fixed In||0.8.2
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #20 from Alexandre Pereira ---
[debug 14:23:24.305305] - Modal : false
[debug 14:23:24.305305] - Demands attention : false
[debug 14:23:24.305305] - Prop1: QFlags(0x8000) Prop2 QFlags()
[debug 14:23:24.306306] - Modal : false
[debug
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #19 from Michail Vourlakos ---
You can the following:
KWindowInfo info(wid, NET::WMState);
if (info.valid()) {
qDebug() << "Modal : " << info.hasState(NET::Modal);
qDebug() << "Demands attention : " <<
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #18 from Alexandre Pereira ---
This is what I am getting:
[debug 13:46:43.304304] - Prop1: QFlags(0x8000) Prop2 QFlags()
[debug 13:46:43.305305] - Prop1: QFlags(0x2000) Prop2 QFlags()
[debug 13:46:43.306306] - Prop1: QFlags(0x8000)
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #17 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #16)
> (In reply to Alexandre Pereira from comment #14)
> > (In reply to Michail Vourlakos from comment #13)
> > > (In reply to Alexandre Pereira from comment #11)
>
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #16 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #14)
> (In reply to Michail Vourlakos from comment #13)
> > (In reply to Alexandre Pereira from comment #11)
>
> The weird thing about it, is, plasmashell is
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #15 from Alexandre Pereira ---
btw, here is the video link:
https://drive.google.com/file/d/1GS13ZZMKeKgwzZbRSma23CXsEIb4QKX7/view?usp=sharing
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #14 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #13)
> (In reply to Alexandre Pereira from comment #11)
> > I tried "strace latte-dock" in a terminal window.
> > There is definitly different behaviour when idle
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #13 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #11)
> I tried "strace latte-dock" in a terminal window.
> There is definitly different behaviour when idle before and after opening
> "SierraCharts" wine app.
>
>
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #12 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #10)
> (In reply to Alexandre Pereira from comment #9)
> > It does have a trial, but its a once, for 2 weeks.
> >
> > Can you make a patch/version that outputs more
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #11 from Alexandre Pereira ---
I tried "strace latte-dock" in a terminal window.
There is definitly different behaviour when idle before and after opening
"SierraCharts" wine app.
I did a video of it, "SierraCharts" app is openned around
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #10 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #9)
> It does have a trial, but its a once, for 2 weeks.
>
> Can you make a patch/version that outputs more debug into the terminal ? Or
> can you tell me where to
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #9 from Alexandre Pereira ---
It does have a trial, but its a once, for 2 weeks.
Can you make a patch/version that outputs more debug into the terminal ? Or can
you tell me where to look for/ which function to analyse, and I will do some
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #8 from Michail Vourlakos ---
I can't think of any other way, isn't providing any trial version?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #7 from Alexandre Pereira ---
unfortunatly the app is a subscription based app ( I am paying for using the
app, which is vital for work )
Is there any way I can help debugging what latte-dock is doing ?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #6 from Alexandre Pereira ---
more testing:
With more windows ( with 3 windows running ), plasmashell keeps using 0%~1%
cpu, but latte-dock increases to 10%~15%.
Seems for each windows, latte-dock increases around 5% cpu.
testing with
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #5 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #4)
> (In reply to Michail Vourlakos from comment #3)
> > (In reply to Alexandre Pereira from comment #2)
> > > (In reply to Michail Vourlakos from comment #1)
> > >
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #4 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #3)
> (In reply to Alexandre Pereira from comment #2)
> > (In reply to Michail Vourlakos from comment #1)
> > > Is this happening with other wine apps?
> >
> > Then I
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #3 from Michail Vourlakos ---
(In reply to Alexandre Pereira from comment #2)
> (In reply to Michail Vourlakos from comment #1)
> > Is this happening with other wine apps?
>
> Then I noticed, that app in question changes the titlebar text
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #2 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #1)
> Is this happening with other wine apps?
Sorry for the late reply.
I have been doing more testing, and no... actually is the only wine app that
does this. (
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #1 from Michail Vourlakos ---
Is this happening with other wine apps?
--
You are receiving this mail because:
You are watching all bug changes.
68 matches
Mail list logo
