https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #49 from Vlad Zahorodnii ---
(In reply to Jonathan Lopes from comment #48)
> 2652 is powerdevil
>
> > $ ps -p 2652 -o command
> > COMMAND
> > /usr/lib/org_kde_powerdevil
Hmm, can you attach gdb to powerdevil and add a breakpoint in
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #48 from Jonathan Lopes ---
(In reply to Vlad Zahorodnii from comment #46)
> > It looks like some application is using
> > ext_idle_notifier_v1::get_idle_notification() with 4294967295ms as timeout
> > value, it's uint so this is kinda
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #47 from Jonathan Lopes ---
Created attachment 166711
--> https://bugs.kde.org/attachment.cgi?id=166711=edit
Kwin IdleDetector breakpoint
(In reply to Vlad Zahorodnii from comment #23)
> Could you please add a breakpoint in
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #46 from Vlad Zahorodnii ---
> It looks like some application is using
> ext_idle_notifier_v1::get_idle_notification() with 4294967295ms as timeout
> value, it's uint so this is kinda valid...
can you apply the patch that I've attached
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #45 from Jonathan Lopes ---
(In reply to Vlad Zahorodnii from comment #23)
> Could you please add a breakpoint in KWin::IdleDetector::IdleDetector
> constructor? I wonder who passes -1 timeout to the IdleDetector.
I'll try to do this right
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #44 from Dāvis ---
Hmm my backtrace is different than Jonathan's.
#0 KWin::IdleDetector::IdleDetector (this=0x55b8773c4220,
timeout=std::chrono::duration = { 4294967295ms }, parent=0x55b877124e50,
this=, timeout=std::chrono::duration = {
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #43 from Vlad Zahorodnii ---
(In reply to bastimeyer123 from comment #41)
> I could only observe the log flooding with the screen locker. Applying the
> two commits
> - 18882eefdecf638e9421116b639bb16a2fca8ce3
> -
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #42 from Vlad Zahorodnii ---
Created attachment 166709
--> https://bugs.kde.org/attachment.cgi?id=166709=edit
patch
can somebody apply the following patch, try to reproduce the bug, and then post
kwin_wayland's log output
--
You are
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #41 from bastimeyer...@gmail.com ---
I could only observe the log flooding with the screen locker. Applying the two
commits
- 18882eefdecf638e9421116b639bb16a2fca8ce3
- aef8796c723e8ec40c19580b2147708aacfb59b0
to 6.0.1 fixed the issue for
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #40 from Vlad Zahorodnii ---
I _think_ that with the patches above kwin should stop flooding the logs with
messages about negative timer interval. BUT somebody still tries to pass a
negative idle interval to kwin, which means that _some_
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #39 from Vlad Zahorodnii ---
Git commit 18882eefdecf638e9421116b639bb16a2fca8ce3 by Vlad Zahorodnii.
Committed on 08/03/2024 at 11:26.
Pushed by vladz into branch 'Plasma/6.0'.
Add timeout assert in IdleDetector
(cherry picked from commit
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #38 from Vlad Zahorodnii ---
Git commit aef8796c723e8ec40c19580b2147708aacfb59b0 by Vlad Zahorodnii.
Committed on 08/03/2024 at 11:27.
Pushed by vladz into branch 'Plasma/6.0'.
Port IdleDetector to QBasicTimer
QBasicTimer is lighter and
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #37 from Vlad Zahorodnii ---
Git commit 68a1e22b643e04cbe813108e4b1c5ec2460b097e by Vlad Zahorodnii.
Committed on 08/03/2024 at 11:36.
Pushed by vladz into branch 'master'.
Guard against invalid timeout values in KIdleTime::addTimeout()
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #36 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/5389
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #35 from Vlad Zahorodnii ---
Git commit e2cbed70609d6505e8c8a89d70373d9fc5f0c2f4 by Vlad Zahorodnii.
Committed on 08/03/2024 at 11:12.
Pushed by vladz into branch 'master'.
Port IdleDetector to QBasicTimer
QBasicTimer is lighter and it
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #34 from Reverier Xu ---
(In reply to Vlad Zahorodnii from comment #32)
> Can somebody share their ~/.config/powerdevilrc alongside with
> ~/.config/kscreenlockerrc please?
~/.config/powerdevilrc
> [AC][Display]
> DimDisplayWhenIdle=false
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #33 from bastimeyer...@gmail.com ---
(In reply to Vlad Zahorodnii from comment #30)
> > I've included this commit (18e414443e500e39bb1ecc3244fceeebb63ceadd) in my
> > kwin build, but it's still flooding the journal after locking the screen
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #32 from Vlad Zahorodnii ---
Can somebody share their ~/.config/powerdevilrc alongside with
~/.config/kscreenlockerrc please?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #31 from Vlad Zahorodnii ---
Git commit 18e414443e500e39bb1ecc3244fceeebb63ceadd by Vlad Zahorodnii.
Committed on 08/03/2024 at 09:09.
Pushed by vladz into branch 'master'.
Add timeout assert in IdleDetector
M +3-0
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #30 from Vlad Zahorodnii ---
> I've included this commit (18e414443e500e39bb1ecc3244fceeebb63ceadd) in my
> kwin build, but it's still flooding the journal after locking the screen
This is rather a sanity check. You could help my building
https://bugs.kde.org/show_bug.cgi?id=482077
Bug Janitor Service changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=482077
bastimeyer...@gmail.com changed:
What|Removed |Added
CC||bastimeyer...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #27 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/5386
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #26 from Vlad Zahorodnii ---
Can somebody share their ~/.config/kscreenlockerrc file please?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #25 from Vlad Zahorodnii ---
(In reply to Vlad Zahorodnii from comment #23)
> Could you please add a breakpoint in KWin::IdleDetector::IdleDetector
> constructor? I wonder who passes -1 timeout to the IdleDetector.
Relevant C++ code just
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #24 from Vlad Zahorodnii ---
if my theory is correct, it's KWinIdleTimePoller::addTimeout; the idle and the
idle-notify-v1 protocols have uint32_t timeout values.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #23 from Vlad Zahorodnii ---
Could you please add a breakpoint in KWin::IdleDetector::IdleDetector
constructor? I wonder who passes -1 timeout to the IdleDetector.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #22 from Jonathan Lopes ---
Created attachment 14
--> https://bugs.kde.org/attachment.cgi?id=14=edit
gdb output from QObject::startTimer breakpoint
(In reply to Dāvis from comment #21)
> Created attachment 166630 [details]
>
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #21 from Dāvis ---
Created attachment 166630
--> https://bugs.kde.org/attachment.cgi?id=166630=edit
kwin_wayland
(In reply to Jonathan Lopes from comment #16)
> [...]
> If I had enough time, I could try to plug a debugger on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #20 from Vlad Zahorodnii ---
Please do not post "me too" comments unless you have valuable information that
can help with reproducing or pinpointing the issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #19 from Gurenko Alex ---
I'm experiencing this on my system with any mouse movement. I have tried Razer
Deathadder V2, Corsair SABRE RGB PRO, Logitech G102 and OG Microsoft Arc Mouse.
Indeed killing the PID stops the spam, just like
https://bugs.kde.org/show_bug.cgi?id=482077
Gurenko Alex changed:
What|Removed |Added
CC||agure...@protonmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=482077
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #18 from Dāvis ---
I'm
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #17 from Jonathan Lopes ---
Just to let you know, 6.0.1 has just hit Arch Linux's stable repositories
today, but the problem is still reproducible.
> Operating System: Arch Linux
> KDE Plasma Version: 6.0.1
> KDE Frameworks Version: 6.0.0
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #16 from Jonathan Lopes ---
(In reply to alex from comment #14)
> (In reply to Jonathan Lopes from comment #11)
> > So, to make it happen, just lock the screen and move your mouse on the lock
> > screen, then unlock
>
> That is not enough
https://bugs.kde.org/show_bug.cgi?id=482077
Reverier Xu changed:
What|Removed |Added
CC||reverier...@outlook.com
--- Comment #15 from
https://bugs.kde.org/show_bug.cgi?id=482077
alex <988a...@mail.ru> changed:
What|Removed |Added
CC||988a...@mail.ru
--- Comment #14 from
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #13 from Nate Graham ---
Cannot reproduce that on my all-Intel hardware, FWIW.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #12 from Jonathan Lopes ---
(In reply to Jonathan Lopes from comment #11)
> I found a way to reliably reproduce it, and a way to reliably stop it from
> happening (although not an ideal one).
>
> So, to make it happen, just lock the screen
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #11 from Jonathan Lopes ---
I found a way to reliably reproduce it, and a way to reliably stop it from
happening (although not an ideal one).
So, to make it happen, just lock the screen and move your mouse on the lock
screen, then unlock.
https://bugs.kde.org/show_bug.cgi?id=482077
Ataberk Özen changed:
What|Removed |Added
CC||ataberkozen...@gmail.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #9 from Jonathan Lopes ---
I just did a test, I disabled Power Saving on my mouse and keyboard, left my
machine idling for an hour, connected through SSH and checked journalctl, no
messages there. I then proceed to unlock it and check
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #8 from Kotori Itsuka ---
My mouse is a Razer Basilisk V2, but I don't have openrazer running or anything
like that.
And I do tend to sleep my machine every night.
Hope that helps.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #7 from Naxdy ---
Though I don't have a razer device, I can confirm that this issue only seems to
pop up for me after a long while of inactivity on my machine (i.e. leaving it
powered up over night). Rebooting solves it until the next
https://bugs.kde.org/show_bug.cgi?id=482077
Jonathan Lopes changed:
What|Removed |Added
CC||joniwe...@gmail.com
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #5 from Kotori Itsuka ---
Operating System: Arch Linux
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Kernel Version: 6.7.6-arch1-2 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #4 from Vlad Zahorodnii ---
Please provide more details about your system. As is, there's not that much
that can make this bug report actionable.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
Vlad Zahorodnii changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=482077
Kotori Itsuka changed:
What|Removed |Added
CC||cmdrkoto...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=482077
Vlad Zahorodnii changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #1 from Naxdy ---
When I rebooted a while back it stopped for a bit, but it's back now. So it may
take a while after opening a session until it shows up?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482077
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org,
|
https://bugs.kde.org/show_bug.cgi?id=482077
Bug Janitor Service changed:
What|Removed |Added
Keywords||qt6
--
You are receiving this mail
53 matches
Mail list logo
