https://bugs.kde.org/show_bug.cgi?id=316348
Vadym Krevs changed:
What|Removed |Added
CC||vkr...@yahoo.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #63 from tagwer...@innerjoin.org ---
(In reply to Szczepan Hołyszewski from comment #62)
> ... How does emulating hardware
> functionality in software make things faster / less CPU intensive? ...
The reference I remember was related to the
https://bugs.kde.org/show_bug.cgi?id=316348
Szczepan Hołyszewski changed:
What|Removed |Added
CC||rula...@wp.pl
--- Comment #62 from
https://bugs.kde.org/show_bug.cgi?id=316348
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--- Comment
https://bugs.kde.org/show_bug.cgi?id=316348
. changed:
What|Removed |Added
CC|dev.rindeal+bugs.kde.org@gm |
|ail.com |
--
You
https://bugs.kde.org/show_bug.cgi?id=316348
logeco...@gmail.com changed:
What|Removed |Added
CC||logeco...@gmail.com
--- Comment #60 from
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #59 from Robin Laing ---
This is from journal logs with one process kscreenlocker_greet at 99%
Apr 06 22:37:36 darkstar.tardis.localdomain kscreenlocker_greet[63511]: Qt:
Session management error: networkIdsList argument is NULL
Apr 06
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #58 from Robin Laing ---
I am running into the situation where kscreenlocker goes to 99% on a regular
basis. I did updates on the weekend and have not seen it since. It seemed to
happen more often the longer I was running between reboots
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #57 from spamdae...@comcast.net ---
Looks like I was a bit too pessimistic. I'm a running a VNC session for use A
and that is not actually using up much CPU. However, when I physically log into
the same machine as user B, then
https://bugs.kde.org/show_bug.cgi?id=316348
spamdae...@comcast.net changed:
What|Removed |Added
CC||spamdae...@comcast.net
--- Comment #56
https://bugs.kde.org/show_bug.cgi?id=316348
Joseph De Veaugh-Geiss changed:
What|Removed |Added
CC||jos...@kde.org
Keywords|
https://bugs.kde.org/show_bug.cgi?id=316348
jmaurin2...@gmail.com changed:
What|Removed |Added
CC||jmaurin2...@gmail.com
--- Comment #55
https://bugs.kde.org/show_bug.cgi?id=316348
Ingo Schmidt-Hammer changed:
What|Removed |Added
CC||ingo.schmidt-ham...@gmx.de
--- Comment
https://bugs.kde.org/show_bug.cgi?id=316348
Keith changed:
What|Removed |Added
CC||fye...@gmail.com
--- Comment #53 from Keith ---
I am
https://bugs.kde.org/show_bug.cgi?id=316348
thelazy...@gmail.com changed:
What|Removed |Added
CC||thelazy...@gmail.com
--- Comment #52
https://bugs.kde.org/show_bug.cgi?id=316348
kenyap.com...@outlook.com changed:
What|Removed |Added
CC|kenyap.com...@outlook.com |
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=316348
kenyap.com...@outlook.com changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=316348
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #50 from Shmerl ---
(In reply to Christoph Feck from comment #49)
> If slideshow is the cause, and you are using Qt 5.9.1, then it probably is a
> duplicate of bug 381000.
Yep, I figured that's the reason. Using static
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #49 from Christoph Feck ---
If slideshow is the cause, and you are using Qt 5.9.1, then it probably is a
duplicate of bug 381000.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #48 from Joachim Wagner ---
It's also still around 9.5% CPU usage in a VM with KVM and both guest and host
using current OpenSUSE Leap 42.3 in a default setup. That's KDE 5.8.7.
For sddm-greeter instead of
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #47 from Robin Laing ---
(In reply to Shmerl from comment #45)
> And just for the reference, it only happens when screen locker is using
> image slideshow. With static image CPU usage is minimal.
I wasn't using a
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #46 from Robin Laing ---
(In reply to Shmerl from comment #44)
> (In reply to Robin Laing from comment #43)
> > Okay, I will create a new bug and keep trying to get any more information.
> >
> > Just wanted to
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #45 from Shmerl ---
And just for the reference, it only happens when screen locker is using image
slideshow. With static image CPU usage is minimal.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=316348
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #43 from Robin Laing ---
Okay, I will create a new bug and keep trying to get any more information.
Just wanted to confirm before opening a new bug report.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #42 from Martin Flöser ---
Whatever problem anyone expriences now, cannot be related with this bug report.
The code base significantly evolved. Any new issues needs to be investigated
again and thus needs a dedicated
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #41 from david.sai...@gmail.com ---
(In reply to Robin Laing from comment #40)
> I think this bug has reappeared.
>
I'm pretty sure no effort was ever made to fix it - it was dismissed as "not a
problem because modern machines are fast
https://bugs.kde.org/show_bug.cgi?id=316348
Robin Laing changed:
What|Removed |Added
CC||me...@telusplanet.net
---
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #39 from Martin Gräßlin ---
> That's the reality with GMA500 Intel graphics. You might still be correct,
> because it's a laptop not a desktop. But I don't quite imagine why you'd make
> that caveat?
The caveat was
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #38 from david.sai...@gmail.com ---
(In reply to Matias Barletta from comment #36)
> @david.sainty
>
> I have felt your pain, even with desktops effects working properly on opengl
> 3.1, kscreenlocker was eating my cpu ALL the time.
>
> I
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #36 from Matias Barletta ---
@david.sainty
I have felt your pain, even with desktops effects working properly on opengl
3.1, kscreenlocker was eating my cpu ALL the time.
I upgraded to the latest KDE Neon User Edition -
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #35 from Martin Gräßlin ---
(In reply to david.sainty from comment #34)
> (In reply to Martin Gräßlin from comment #30)
> > According to the backtrace: you are using llvmpipe, which means OpenGL is
> > emulated on the
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #34 from david.sai...@gmail.com ---
(In reply to Martin Gräßlin from comment #30)
> According to the backtrace: you are using llvmpipe, which means OpenGL is
> emulated on the CPU. Of course that's not going to be efficient.
But, what if
https://bugs.kde.org/show_bug.cgi?id=316348
david.sai...@gmail.com changed:
What|Removed |Added
CC||david.sai...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #33 from Martin Gräßlin ---
> This is a default install of OpenSUSE 42.1 in a VM. Hardware graphics
> acceleration is not an option
Hardware graphics acceleration in VM is nowadays an option. VMware, VBox, KVM
all
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #32 from Joachim Wagner ---
(In reply to Martin Gräßlin from comment #30)
> According to the backtrace: you are using llvmpipe, which means OpenGL is
> emulated on the CPU. Of course that's not going to be
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #31 from Matias Barletta ---
This is a more complete bt
Thread 9 (Thread 0x7f8678664700 (LWP 21290)):
#0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x7f868984bbd2 in ?? () from
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #30 from Martin Gräßlin ---
According to the backtrace: you are using llvmpipe, which means OpenGL is
emulated on the CPU. Of course that's not going to be efficient.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #29 from Joachim Wagner ---
Maybe useful to see which of the above threads consumes CPU (command "top" + H
for threads):
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
3557 sddm
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #28 from Joachim Wagner ---
Thanks for providing the command. Note to others: "help t", "help t a", etc. on
the gdb prompt tells you what it does.
(gdb) help t a a
Apply a command to all threads.
(gdb) t a a bt
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #27 from Martin Gräßlin ---
Thanks for the backtraces. Both show the main thread in the event loop. Which
means we don't see anything.
Could you please get all thread traces. Use "t a a bt" for that.
--
You are
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #26 from Joachim Wagner ---
On OpenSUSE Leap 42.1
(steps: find pid, e.g. from "top", run gdb -p pid and enter "backtrace" on the
"(gdb)" prompt)
#0 0x7fa9073eebbd in poll () at /lib64/libc.so.6
#1
https://bugs.kde.org/show_bug.cgi?id=316348
Matias Barletta changed:
What|Removed |Added
CC||m...@lionix.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=316348
rindeal changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #23 from Martin Gräßlin ---
I just locked the desktop, switched to another vt, run top and I couldn't even
find kscreenlocker_greet in the list.
Those experiencing the problem need to help us: please gdb into the
46 matches
Mail list logo