https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #15 from Christoph Feck ---
Thanks for the update. Please set the status to REOPEN if you add new
information.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #14 from waldauf ---
In this time - due coronavirus - I'm working from my home and the problems
described here I had at work. As soon as will be possible I'll retest the whole
issue. If the problems will persistent I send debug information.
https://bugs.kde.org/show_bug.cgi?id=416914
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #12 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
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #11 from Christoph Feck ---
> ptrace: Operation not permitted.
Please ask for help in a forum of your distribution how to generate a backtrace
for this case. gdb should be able to attach to a running process, unless the
process has already
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #10 from waldauf ---
I need your help. I'm trying to backtrace plasmashell.
There are all processes with plasmashell:
UID PIDPPID C STIME TTY TIME CMD
root1348 868 0 17:09 ?00:00:00 /usr/lib/sddm/
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #9 from David Edmundson ---
if plasmashell is frozen, lets get a backtrace of plasmashell in the frozen
state.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #8 from waldauf ---
(In reply to David Edmundson from comment #6)
> I'm very confused by the original report.
>
> Report says plasmashell is frozen
> And that kwin is using max CPU
>
> The backtrace is of kwin crashing after being closed.
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #7 from waldauf ---
(In reply to Nate Graham from comment #5)
> Cannot reproduce the issue. I can connect an external screen and there's no
> freeze.
What I discovered this freezing occurs when you connect two external monitors.
If is there
https://bugs.kde.org/show_bug.cgi?id=416914
David Edmundson changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #5 from Nate Graham ---
Cannot reproduce the issue. I can connect an external screen and there's no
freeze.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #4 from waldauf ---
Hello, is there some progress? I can confirm this problem on two laptopts -
Lenovo and Dell.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #3 from waldauf ---
The problem still persists in new the KDE version:
Operating System: Arch Linux
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Kernel Version: 5.5.2-arch2-2
OS Type: 64-bit
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #2 from waldauf ---
Is here anybody who can solve this problem?
My next error which I captured during restart kdeplasma:
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
QQuickItem::stackAfter: Cannot sta
https://bugs.kde.org/show_bug.cgi?id=416914
David Edmundson changed:
What|Removed |Added
Severity|critical|crash
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=416914
--- Comment #1 from waldauf ---
Upgrade qt5-base didn't help:
qt5-base (5.14.0-3 -> 5.14.1-1)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416914
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org,
|
17 matches
Mail list logo
