[kwin] [Bug 466777] Black screen kwin_wayland death

https://bugs.kde.org/show_bug.cgi?id=466777 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com -- You are receiving this mail

[kwin] [Bug 466777] New: Black screen kwin_wayland death

https://bugs.kde.org/show_bug.cgi?id=466777 Bug ID: 466777 Summary: Black screen kwin_wayland death Classification: Plasma Product: kwin Version: 5.27.2 Platform: Ubuntu OS: Linux Status: REPORTED Seve

[kwin] [Bug 450069] Plasma 5.24 freezes/black screen on wake from sleep

https://bugs.kde.org/show_bug.cgi?id=450069 --- Comment #6 from m1st0 --- Any helpful relationship? Xwayland crash in gdm as screen off and touchscreen detach. https://bugs.launchpad.net/oem-priority/+bug/1948894 -- You are receiving this mail because: You are watching all bug changes.

[ksmserver] [Bug 449948] After kwin_wayland crashes and restarts or is manually restarted, Reboot, shutdown and logout do not work due to ksmserver relying on XWayland which also died and did not come

https://bugs.kde.org/show_bug.cgi?id=449948 --- Comment #7 from m1st0 --- Any helpful relationship? Xwayland crash in gdm as screen off and touchscreen detach. https://bugs.launchpad.net/oem-priority/+bug/1948894 -- You are receiving this mail because: You are watching all bug changes.

[ksmserver] [Bug 449948] After kwin_wayland crashes and restarts or is manually restarted, Reboot, shutdown and logout do not work due to ksmserver relying on XWayland which also died and did not come

https://bugs.kde.org/show_bug.cgi?id=449948 --- Comment #6 from m1st0 --- Any helpful relationship? Xwayland crash in gdm as screen off and touchscreen detach. https://bugs.launchpad.net/oem-priority/+bug/1948894 On Mon, Apr 4, 2022, 11:27 AM postix wrote: > https://bugs.kde.org/show_bug.

[kwin] [Bug 450069] Plasma 5.24 freezes/black screen on wake from sleep

https://bugs.kde.org/show_bug.cgi?id=450069 --- Comment #5 from m1st0 --- I wonder if this has a relation. Xwayland crash in gdm as screen off and touchscreen detach. https://bugs.launchpad.net/oem-priority/+bug/1948894 -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 450069] Plasma 5.24 freezes/black screen on wake from sleep

https://bugs.kde.org/show_bug.cgi?id=450069 m1st0 changed: What|Removed |Added Version|5.24.3 |5.24.4 -- You are receiving this mail because: You

[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything

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

[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything

https://bugs.kde.org/show_bug.cgi?id=448517 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com -- You are receiving this mail

[krunner] [Bug 427069] [wayland] Krunner starts on the left-most screen instead of screen with the cursor on it

https://bugs.kde.org/show_bug.cgi?id=427069 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com -- You are receiving this mail

[plasmashell] [Bug 450069] Plasma 5.24 freezes/black screen on wake from sleep

https://bugs.kde.org/show_bug.cgi?id=450069 m1st0 changed: What|Removed |Added Version|5.24.0 |5.24.3 -- You are receiving this mail because: You

[plasmashell] [Bug 450069] Plasma 5.24 freezes/black screen on wake from sleep

https://bugs.kde.org/show_bug.cgi?id=450069 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com --- Comment #4 from m1st0 --- I

[ksmserver] [Bug 449948] After kwin_wayland crashes and restarts or is manually restarted, Reboot, shutdown and logout do not work due to ksmserver relying on XWayland which also died and did not come

https://bugs.kde.org/show_bug.cgi?id=449948 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com -- You are receiving this mail

[yakuake] [Bug 445158] Yakuake does not open on the screen where the mouse pointer is

https://bugs.kde.org/show_bug.cgi?id=445158 --- Comment #3 from m1st0 --- (In reply to m1st0 from comment #2) > EXPECTED RESULT > Yakuake should open on the screen where the mouse pointer is on Wayland, > like KRunner or Yakuake does on X11. Sorry, should have confirmed rather t

[bugs.kde.org] [Bug 334299] edit function for comments

https://bugs.kde.org/show_bug.cgi?id=334299 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com -- You are receiving this mail

[yakuake] [Bug 445158] Yakuake does not open on the screen where the mouse pointer is

https://bugs.kde.org/show_bug.cgi?id=445158 m1st0 changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You

[krunner] [Bug 445157] KRunner always opens on a particular screen in Wayland (unlike X11, where it opens where the mouse is)

https://bugs.kde.org/show_bug.cgi?id=445157 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com -- You are receiving this mail

[yakuake] [Bug 445158] Yakuake does not open on the screen where the mouse pointer is

https://bugs.kde.org/show_bug.cgi?id=445158 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com --- Comment #2 from m1st0

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #51 from m1st0 --- (In reply to Luke-Jr from comment #50) > $ loginctl lock-session > Failed to issue method call: Is a directory > $ loginctl unlock-session > Failed to issue method call: Is a directory I tried to look up

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #49 from m1st0 --- Sorry, missed mentioning examples for your own session: loginctl lock-session; sleep 3 loginctl unlock-session Use as needed. -- You are receiving this mail because: You are watching all bug changes.

[kscreensaver] [Bug 314989] Screen locker won't unlock/deactivate using dbus

https://bugs.kde.org/show_bug.cgi?id=314989 --- Comment #48 from m1st0 --- Simple enough now using loginctl as a privileged user for example: sudo loginctl lock-sessions; sleep 3 sudo loginctl unlock-sessions Therefore without specifically needing to call with sudo, you can easily

[systemsettings] [Bug 384250] PlasmaShell and systemsettings crash on Intel GPU 530

https://bugs.kde.org/show_bug.cgi?id=384250 --- Comment #5 from m1st0 --- (In reply to m1st0 from comment #4) Possibly the upgrade from Mesa version: 17.1.4 to 17.2.0. -- You are receiving this mail because: You are watching all bug changes.

[systemsettings] [Bug 384250] PlasmaShell and systemsettings crash on Intel GPU 530

https://bugs.kde.org/show_bug.cgi?id=384250 m1st0 changed: What|Removed |Added Keywords|drkonqi | Resolution|--- |FIXED

[systemsettings] [Bug 384250] PlasmaShell and systemsettings crash on Intel GPU 530

https://bugs.kde.org/show_bug.cgi?id=384250 m1st0 changed: What|Removed |Added CC||mistr...@gmail.com -- You are receiving this mail

[systemsettings] [Bug 384250] PlasmaShell and systemsettings crash on Intel GPU 530

https://bugs.kde.org/show_bug.cgi?id=384250 --- Comment #3 from m1st0 --- I have the three following symptoms, which I believe are related in some way but I cannot correlate them yet: * SDDM Breeze Theme is all over the place on 2 monitors. Can't see the password text box and alignment of

[systemsettings] [Bug 384250] PlasmaShell and systemsettings crash on Intel GPU 530

https://bugs.kde.org/show_bug.cgi?id=384250 m1st0 changed: What|Removed |Added Version|5.10.5 |5.9.5 --- Comment #2 from m1st0 --- Here is output of

[systemsettings] [Bug 384250] PlasmaShell and systemsettings crash on Intel GPU 530

https://bugs.kde.org/show_bug.cgi?id=384250 m1st0 changed: What|Removed |Added Version|5.9.5 |5.10.5 -- You are receiving this mail because: You

[systemsettings] [Bug 384250] New: PlasmaShell and systemsettings crash on Intel GPU 530

https://bugs.kde.org/show_bug.cgi?id=384250 Bug ID: 384250 Summary: PlasmaShell and systemsettings crash on Intel GPU 530 Product: systemsettings Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRM