https://bugs.kde.org/show_bug.cgi?id=432029
Nate Graham changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #15 from Andrey ---
May be, it's just hard to read it here so I think attaching them additionally
doesn't hurt.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #14 from Nate Graham ---
Backtraces need to be inserted as comments so that their text they appears in
search results. Attachments aren't indexed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #13 from Andrey ---
One more thing:
could you attach these backtraces as files?
It would be easier to analyze.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432029
Nate Graham changed:
What|Removed |Added
Severity|critical|crash
CC|
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #12 from Andrey ---
Ah, seems we got update problem..
It happens from time to time, and in my experience it rather unpredictable and
hard to debug, so it's good we catch it here!
I'll rise attention to this problem, and from your side you co
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #11 from Vladyslav ---
(In reply to Andrey from comment #10)
> Thanks Vladyslav,
> I'm not sure I'm experienced enough to help you here,
> but are you sure it's not something with your setup?
> Have you tried on new user/clean install in VM
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #10 from Andrey ---
Thanks Vladyslav,
I'm not sure I'm experienced enough to help you here,
but are you sure it's not something with your setup?
Have you tried on new user/clean install in VM maybe?
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #9 from Vladyslav ---
I've installed more debug packages and in crash helper, there is the following
backtrace, it's more informative as I see:
Application: Plasma (plasmashell), signal: Segmentation fault
[KCrash Handler]
#4 QQmlRefPoint
https://bugs.kde.org/show_bug.cgi?id=432029
Vladyslav changed:
What|Removed |Added
Summary|plasmashell crashes on |plasmashell crashes on
|start bec
https://bugs.kde.org/show_bug.cgi?id=432029
Andrey changed:
What|Removed |Added
Flags||Wayland+
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #8 from Vladyslav ---
Here are logs from coredump, hopefully, they will help:
Jan 24 19:54:04 linux-ua4q systemd-coredump[3178]: Process 3114 (plasmashell)
of user 1000 dumped core.
Stack
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #7 from David Edmundson ---
Git commit 55c390cc874dd0cd5496f180d13845673265db80 by David Edmundson, on
behalf of Andrey Butirsky.
Committed on 24/01/2021 at 15:03.
Pushed by davidedmundson into branch 'Plasma/5.21'.
[keyboard applet] fix Ty
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #6 from Andrey ---
Git commit f60dcd7b6ba91b8b92571247d77bb2322d469387 by Andrey Butirsky.
Committed on 24/01/2021 at 15:00.
Pushed by butirsky into branch 'master'.
[keyboard applet] fix TypeError garbage in log
While unharmful (JS checks
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #5 from Andrey ---
If you have coredumpctl i think this is the simplest,
the commands to go is something like this:
$ coredumpctl gdb
then inside opened gdb:
bt
You might need to install dev packages with debugging symbols, the command
abo
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #4 from Vladyslav ---
(In reply to Andrey from comment #1)
> Hi,
> I also have these org.kde.plasma.keyboardlayout errors but tend to expect
> they are normal.
> Backtrace could be helpful.
> But first, could you rename
> /usr/share/plasma/p
https://bugs.kde.org/show_bug.cgi?id=432029
Andrey changed:
What|Removed |Added
Component|Keyboard Layout |generic-crash
--- Comment #3 from Andrey ---
Yeah, it
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #2 from Vladyslav ---
Yes, even without keyboardlayout plasmashell still doesn't start:
```
Jan 24 13:57:10 linux-ua4q at-spi-bus-launcher[22321]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 24 13:57:10 linux-ua4q at-sp
https://bugs.kde.org/show_bug.cgi?id=432029
--- Comment #1 from Andrey ---
Hi,
I also have these org.kde.plasma.keyboardlayout errors but tend to expect they
are normal.
Backtrace could be helpful.
But first, could you rename
/usr/share/plasma/plasmoids/org.kde.plasma.keyboardlayout/contents/ui/m
19 matches
Mail list logo
