https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #14 from owl-from-hogva...@protonmail.com ---
Created attachment 145881
--> https://bugs.kde.org/attachment.cgi?id=145881=edit
kded5 trace
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #13 from owl-from-hogva...@protonmail.com ---
(In reply to owl-from-hogvarts from comment #10)
> Created attachment 145873 [details]
> trace of most recent plasmashell crash
>
> Wierd thing: plasma does not crash anymore (or does not report
https://bugs.kde.org/show_bug.cgi?id=448845
owl-from-hogva...@protonmail.com changed:
What|Removed |Added
Version|5.23.4 |5.23.5
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #12 from owl-from-hogva...@protonmail.com ---
Now plasmashell report such message: starting invalid corona
org.kde.plasma.desktop
There are enumerouse warnings from theme installed about properties that cant
be resolved
--
You are
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #11 from owl-from-hogva...@protonmail.com ---
Things getting more wierd: plasmashell does not crash anymore. I still gets
Black destoo when loggin via sddm. But i can succesfully load plasma when
starting manually from termunal like startx
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #10 from owl-from-hogva...@protonmail.com ---
Created attachment 145873
--> https://bugs.kde.org/attachment.cgi?id=145873=edit
trace of most recent plasmashell crash
Wierd thing: plasma does not crash anymore (or does not report about
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #9 from Nate Graham ---
We need a backtrace from plasmashell, not kded5 (that crash should be reported
separately, in another bug report).
To do this, you run `coredumpctl gdb `, which in this
case looks to be 5364.
So you would run
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #8 from owl-from-hogva...@protonmail.com ---
Created attachment 145735
--> https://bugs.kde.org/attachment.cgi?id=145735=edit
other available backtraces
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #7 from owl-from-hogva...@protonmail.com ---
Created attachment 145734
--> https://bugs.kde.org/attachment.cgi?id=145734=edit
kded5 backtrace
i recompiled plasma-workspace package which provides plasmashell and
startplasma-x11. Here is
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #6 from owl-from-hogva...@protonmail.com ---
(In reply to Nate Graham from comment #5)
> Depends on where the crash is. Usually just KDE stuff is enough.
So if the plasma itself crashes on startup, what packages should i rebuild with
debug
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #5 from Nate Graham ---
Depends on where the crash is. Usually just KDE stuff is enough.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #4 from owl-from-hogva...@protonmail.com ---
(In reply to Nate Graham from comment #3)
> Can you please attach a *backtrace* of the crash? not a journalctl log, a
> backtrace. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
https://bugs.kde.org/show_bug.cgi?id=448845
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #2 from owl-from-hogva...@protonmail.com ---
Created attachment 145674
--> https://bugs.kde.org/attachment.cgi?id=145674=edit
journalctl log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448845
--- Comment #1 from owl-from-hogva...@protonmail.com ---
Kde framework version: 5.89
Qt: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
15 matches
Mail list logo
