https://bugs.kde.org/show_bug.cgi?id=407653
Antonio Rojas changed:
What|Removed |Added
Resolution|WORKSFORME |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=407653
mthw0 changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=407653
--- Comment #14 from David Edmundson ---
Our seccomp filter is blocking something in wl_cursor_theme_load
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407653
--- Comment #13 from David Edmundson ---
Ignore my comment above, I was mixing up the SDDM crash which was QML related
in upstream Qt.
Yes, lets leave this open as best case with the Qt fix we still have an
incorrect cursor theme. It probably means an
https://bugs.kde.org/show_bug.cgi?id=407653
--- Comment #12 from Antonio Rojas ---
The crash is fixed upstream with
https://codereview.qt-project.org/c/qt/qtwayland/+/262349
However, the Plasma issue that was triggering the crash still holds: the screen
locker seems to be requesting an invalid c
https://bugs.kde.org/show_bug.cgi?id=407653
--- Comment #11 from mthw0 ---
(In reply to David Edmundson from comment #10)
> I have one on phab
Could you share it here?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407653
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #10 fro
https://bugs.kde.org/show_bug.cgi?id=407653
--- Comment #9 from mthw0 ---
(In reply to Antonio Rojas from comment #8)
> Reported upstream https://bugreports.qt.io/browse/QTBUG-75920
Would it be possible for you to create a (temporary) patch/workaround for Arch?
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=407653
--- Comment #8 from Antonio Rojas ---
Reported upstream https://bugreports.qt.io/browse/QTBUG-75920
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407653
Antonio Rojas changed:
What|Removed |Added
CC||tro...@free.fr
--- Comment #7 from Antonio Roja
https://bugs.kde.org/show_bug.cgi?id=407653
--- Comment #6 from Antonio Rojas ---
(In reply to Fabian Vogt from comment #5)
> The backtrace points to
> https://github.com/qt/qtwayland/commit/
> 021bd4d7ed1f4221a0132e21ef0ee5b07f74be3e being involved. I currently don't
> have a system with Qt 5.13
https://bugs.kde.org/show_bug.cgi?id=407653
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--- Comment #5 from Fabian
https://bugs.kde.org/show_bug.cgi?id=407653
mthw0 changed:
What|Removed |Added
CC||matejm98m...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=407653
--- Comment #3 from Antonio Rojas ---
This is also reproducible with 5.15.5, so actually a Qt 5.13 issue
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407653
Antonio Rojas changed:
What|Removed |Added
CC||aro...@archlinux.org
--- Comment #2 from Antoni
https://bugs.kde.org/show_bug.cgi?id=407653
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #1 from Patrick
16 matches
Mail list logo
