https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #22 from Martin Gräßlin ---
(In reply to Lóránt Farkas from comment #21)
> Created attachment 101692 [details]
> kstart5 plasmashell backtrace
That's a crash of kstart5 - please report a new bug for that one.
--
You
https://bugs.kde.org/show_bug.cgi?id=356175
John Rowley changed:
What|Removed |Added
CC|john.rowle...@gmail.com |
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #20 from Lóránt Farkas ---
With
$kstart5 plasmashell
I got backtrace, attached here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #19 from Christoph Feck ---
Please use "kstart5" instead of "kstart" when running KF5 applications.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #18 from Lóránt Farkas ---
The coredump in comment 15 is a clean start and crash through sddm.
As the ktorrent starts I can open a dolphin (it starts clean) and I can run
commands though the konsole.
If a run the
https://bugs.kde.org/show_bug.cgi?id=356175
eduardo changed:
What|Removed |Added
CC||edoantoni...@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #16 from Martin Gräßlin ---
@Lorant: is this the same backtrace as the one in this bug report?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #15 from Lóránt Farkas ---
I did half an hour ago, after a full system refresh.
I still have have crash. The spalsh screen shows up, then the ktorrent windows
shows up, and that's all. Now at least I have a coredump.
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #14 from darkba...@linuxsystems.it ---
Also I'm not able to test it anymore on the same machine, so I agree to close
it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356175
Martin Gräßlin changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=356175
David Edmundson changed:
What|Removed |Added
Component|general |generic-wayland
https://bugs.kde.org/show_bug.cgi?id=356175
Störm Poorun changed:
What|Removed |Added
CC||s...@olan.org
--
You are
https://bugs.kde.org/show_bug.cgi?id=356175
Lóránt Farkas changed:
What|Removed |Added
CC||farkasl...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #11 from Martin Gräßlin ---
(In reply to John Rowley from comment #9)
> Running startplasmacompositor via .xinitrc
Erm I hope you see the problem with trying to start wayland through *X*initrc.
> I'm running Slackware
https://bugs.kde.org/show_bug.cgi?id=356175
Martin Gräßlin changed:
What|Removed |Added
Attachment #98149|text/x-log |text/plain
mime
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #10 from John Rowley ---
Created attachment 98149
--> https://bugs.kde.org/attachment.cgi?id=98149=edit
Session log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #9 from John Rowley ---
I'm getting the same issue here, too.
Running startplasmacompositor via .xinitrc results in a black screen with a
Breeze-themed pointer. Pressing Alt-Space results in a delay and then
https://bugs.kde.org/show_bug.cgi?id=356175
John Rowley changed:
What|Removed |Added
CC||john.rowle...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=356175
Marco Martin changed:
What|Removed |Added
CC||wawalkenho...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #4 from darkba...@linuxsystems.it ---
With latest git snapshot I get the "black screen with cursor" despite the kinit
patch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #5 from Brandon Gandy ---
(In reply to darkbasic from comment #4)
> With latest git snapshot I get the "black screen with cursor" despite the
> kinit patch.
Same issue here. It's not the login manager since I've tried
https://bugs.kde.org/show_bug.cgi?id=356175
Patrick Auernig changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #6 from Patrick Auernig ---
*** Bug 355843 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356175
Brandon Gandy changed:
What|Removed |Added
CC||xen...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #2 from Martin Gräßlin ---
Do you have the abort message Qt prints?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356175
Marco Martin changed:
What|Removed |Added
CC||mgraess...@kde.org,
https://bugs.kde.org/show_bug.cgi?id=356175
--- Comment #3 from darkba...@linuxsystems.it ---
This is the only log I have: https://paste.lugons.org/show/9740/
I don't know where to find the QT abort message you are talking about.
I forgot to say that if went so far it's because I disable OOM
27 matches
Mail list logo