https://bugs.kde.org/show_bug.cgi?id=427471
Emanuele Spirito changed:
What|Removed |Added
CC||emaster...@gmail.com
--- Comment #7 from Ema
https://bugs.kde.org/show_bug.cgi?id=427471
Paschalis Veskos changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=427471
--- Comment #2 from roa...@protonmail.com ---
(In reply to Elvis Angelaccio from comment #1)
> Is this still reproducible?
>
> If yes, please get a stacktrace after the CPU usage goes up.
> You can run "gdb dolphin" from konsole, then press CTRL+C and t
https://bugs.kde.org/show_bug.cgi?id=427471
--- Comment #3 from roa...@protonmail.com ---
okay, so its using up anywhere from 18-24% overall CPU (2 threads entirely).
here's the backtrace from gdb:
> #0 0x77dc537f in poll () at /usr/lib/libc.so.6
> #1 0x73cdddef in () at /usr/
https://bugs.kde.org/show_bug.cgi?id=427471
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=427471
--- Comment #4 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=427471
Elvis Angelaccio changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=427471
Oliver Redner changed:
What|Removed |Added
CC||redner@arcor.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=427471
simon.gra...@pm.me changed:
What|Removed |Added
CC||simon.gra...@pm.me
--
You are receiving th
