https://bugs.kde.org/show_bug.cgi?id=448517
Nate Graham changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=449948
https://bugs.kde.org/show_bug.cgi?id=448517
Nate Graham changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #25 from Bernie Innocenti ---
(In reply to Nate Graham from comment #23)
> Indeed, it is likely that this is the same as Bug 449948, which says that
> the issue is 100% reproducible if kwin_wayland has crashed and restarted
> automatically,
https://bugs.kde.org/show_bug.cgi?id=448517
Nate Graham changed:
What|Removed |Added
CC||herzensch...@gmail.com
--- Comment #24 from Nate
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #23 from Nate Graham ---
Indeed, it is likely that this is the same as Bug 449948, which says that the
issue is 100% reproducible if kwin_wayland has crashed and restarted
automatically, or was killed and restarted manually.
Can everyone
https://bugs.kde.org/show_bug.cgi?id=448517
m1st0 changed:
What|Removed |Added
Version|5.23.90 |5.24.4
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=448517
m1st0 changed:
What|Removed |Added
CC||mistr...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=448517
postix changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=448517
Dennis Schridde changed:
What|Removed |Added
CC||devuran...@gmx.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=448517
Oliver Klee changed:
What|Removed |Added
CC||kde...@oliverklee.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #22 from Bernie Innocenti ---
I wonder if there's any relation to bug #449948?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448517
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=448517
Nate Graham changed:
What|Removed |Added
CC||sebastian.p...@gmail.com
--- Comment #21 from
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #20 from Bernie Innocenti ---
I'm running Fedora 36 with Plasma 5.24.0 and I just installed the updates to
5.24.1.
I was going to restart the session to start using the updated desktop
components, but I hit this bug again.
ksmserver was
https://bugs.kde.org/show_bug.cgi?id=448517
Fushan Wen changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |
|ma/plasma-workspace/-/commi |
https://bugs.kde.org/show_bug.cgi?id=448517
Nate Graham changed:
What|Removed |Added
Ever confirmed|1 |0
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #18 from Viorel-Cătălin Răpițeanu ---
(In reply to Fushan Wen from comment #15)
> (In reply to Bernie Innocenti from comment #13)
> > (In reply to Nate Graham from comment #12)
> > > Interesting. If you get it out of that state (e.g. by
https://bugs.kde.org/show_bug.cgi?id=448517
Fushan Wen changed:
What|Removed |Added
Resolution|FIXED |WAITINGFORINFO
--- Comment #17 from Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #16 from Nate Graham ---
Fushan, you just marked this as fixed by a commit that's a week old but you
said you can reproduce it today. Did you not yet have that commit when you
tested it?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=448517
Fushan Wen changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=448517
Fushan Wen changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #14 from Fushan Wen ---
I can reproduce it by running `systemctl --user stop plasma-ksmserver.service`
So I guess it's related to crashes or unresponsiveness of ksmserver?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=448517
Bernie Innocenti changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #12 from Nate Graham ---
Interesting. If you get it out of that state (e.g. by killing and restarting
plasmashell) does the hang-on-logout issue still happen? If not, then it may be
a separate issue.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #11 from Bernie Innocenti ---
It just happened to me again with plasmashell from
plasma-workspace-5.23.90-2.fc36.x86_64.
Just before this, I did "something" that made the panel miss some button
release event, and the task bar was
https://bugs.kde.org/show_bug.cgi?id=448517
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=448517
Viorel-Cătălin Răpițeanu changed:
What|Removed |Added
CC||rapiteanu.cata...@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=448517
Nate Graham changed:
What|Removed |Added
Keywords||wayland
--- Comment #9 from Nate Graham ---
I
https://bugs.kde.org/show_bug.cgi?id=448517
Fushan Wen changed:
What|Removed |Added
CC||qydwhotm...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #8 from Nate Graham ---
Yep, I see the same symptoms.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #7 from Bernie Innocenti ---
I captured the the journal just before a plasmashell crash:
---cut---
trying to show an empty dialog
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.svg: :303:258: Could not add child
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #6 from Bernie Innocenti ---
Created attachment 145783
--> https://bugs.kde.org/attachment.cgi?id=145783=edit
Plasmashell freezing when you click Logout.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448517
Bernie Innocenti changed:
What|Removed |Added
CC||ber...@codewiz.org
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #4 from Nate Graham ---
SDDM 0.19.0
Switching between VTs works, but does not un-wedge plasma for me. If I return
to the VT with the session on it, Plasma is still stuck for a bit.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #3 from Linus Dierheimer ---
SDDM: 0.19.0-7
Switching to another TTY just brings up the usual console based login.
Switching back to plasma doesn't change anything there, if you are fast enough
its sometimes even still frozen. Switching to
https://bugs.kde.org/show_bug.cgi?id=448517
--- Comment #2 from David Edmundson ---
Can you include SDDM version?
Does switching VTs (control+alt f2 etc) fix anything?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448517
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Summary|Logout of
37 matches
Mail list logo