https://bugs.kde.org/show_bug.cgi?id=463659
Nate Graham changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #16 from Enrico ---
Hello, since I'm not having this bug anymore (5.27) and the QTBUG-110484 is
closed, I think we can close this bug report too
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #15 from Enrico ---
Hello, I'm planning to change my PC in the next days and I'll reinstall the
whole system. i don't know if the bug will happen again. It seems also less
frequent since the last updates.
Let me know if it could be useful t
https://bugs.kde.org/show_bug.cgi?id=463659
Nate Graham changed:
What|Removed |Added
URL||https://bugreports.qt.io/br
|
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #14 from David Redondo ---
I've filed https://bugreports.qt.io/browse/QTBUG-110484
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #13 from David Redondo ---
We should be protected against SIGPIPE in
https://invent.kde.org/qt/qt/qtwayland/-/blob/kde/5.15/src/client/qwaylanddatasource.cpp#L84
(and in KGuiAddons which the first backtrace points to
https://invent.kde.org/
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #12 from Enrico ---
Created attachment 155467
--> https://bugs.kde.org/attachment.cgi?id=155467&action=edit
The button that disappears after the crash
I don't know if it's relevant, but the only difference I noted before and after
the cra
https://bugs.kde.org/show_bug.cgi?id=463659
Nate Graham changed:
What|Removed |Added
CC||k...@david-redondo.de
Keywords|
https://bugs.kde.org/show_bug.cgi?id=463659
Enrico changed:
What|Removed |Added
Resolution|BACKTRACE |---
Status|NEEDSINFO |RE
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #9 from Enrico ---
Hello, I've reproduced the crash and created the following backtrace after
installing the . I'm not sure it gives you more data than the preovious one. It
seems different, but I can't understand if it's useful.
Thread 1 "
https://bugs.kde.org/show_bug.cgi?id=463659
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=463659
Enrico changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #6 from Enrico ---
Hello,
I've started the "gdb plasmashell" and reproduced the crash.
gdb reports
"[New process 714]
[Inferior 1 (process 714) exited with code 01]"
but when I enter "backtrace" it says
"(gdb) backtrace
No stack."
Maybe p
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #5 from Enrico ---
(In reply to David Edmundson from comment #4)
> From the forum thread:
> >I run "sudo gdb plasmashell [PID]" or "sudo gdb [PID]" and it seems to work,
> >but the whole plasmashell freezes.
> you need to type "continue" in
https://bugs.kde.org/show_bug.cgi?id=463659
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
Resolution|
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #3 from Enrico ---
Created attachment 154926
--> https://bugs.kde.org/attachment.cgi?id=154926&action=edit
second log from journalctl
It just happened again, without any X11 application running. I attach the new
journalctl hoping it can b
https://bugs.kde.org/show_bug.cgi?id=463659
Enrico changed:
What|Removed |Added
Version|5.25.4 |5.26.4
--- Comment #2 from Enrico ---
I've selected t
https://bugs.kde.org/show_bug.cgi?id=463659
--- Comment #1 from Bug Janitor Service ---
Thank you for the bug report!
Please note that Plasma 5.25.4 is not supported for much longer by KDE;
supported versions are 5.24, and 5.26 or newer.
If at all possible please upgrade to a supported version
18 matches
Mail list logo
