[plasmashell] [Bug 465570] New: Primary display lost wallpaper (showing black screen) after waking up

2023-02-10 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=465570 Bug ID: 465570 Summary: Primary display lost wallpaper (showing black screen) after waking up Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Archlinux

[plasmashell] [Bug 465570] Primary display lost wallpaper (showing black screen) after waking up

2023-02-10 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=465570 --- Comment #1 from P Shao --- I want to make a correction: I just tested again by switching B into primary and now after being turned on B shows a black screen. So this issue appears only affect whichever is being set as the **primary** screen

[plasmashell] [Bug 465570] Primary display lost wallpaper (showing black screen) after waking up in Wayland

2023-02-10 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=465570 P Shao changed: What|Removed |Added Summary|Primary display lost|Primary display lost |wallpaper

[plasmashell] [Bug 465570] Primary display lost wallpaper (showing black screen) after waking up in Wayland

2023-02-10 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=465570 --- Comment #2 from P Shao --- Also want to add that I tested again using KDE Neon unstable, version 5.27.80, using exactly the same configuration as my regular environment and I can **not** reproduce this bug in 5.27.80. So there is a high chance this

[kwin] [Bug 465887] New: Primary display blinks/flickers once upon waking up from sleep in Wayland session

2023-02-16 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=465887 Bug ID: 465887 Summary: Primary display blinks/flickers once upon waking up from sleep in Wayland session Classification: Plasma Product: kwin Version: 5.27.0 Platform: Other

[kde] [Bug 456696] "QSocketNotifier: Can only be used with threads started with QThread" everywhere

2023-08-31 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=456696 P Shao changed: What|Removed |Added CC||shallp...@gmail.com --- Comment #3 from P Shao --- I

[kde] [Bug 456696] "QSocketNotifier: Can only be used with threads started with QThread" everywhere

2023-09-01 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=456696 --- Comment #4 from P Shao --- (In reply to Nate Graham from comment #1) > > I don't know whether this is a problem with libQt or with the use of it. > I'm CCing some very smart people who may be able to determine which one it >

[kde] [Bug 456696] "QSocketNotifier: Can only be used with threads started with QThread" everywhere

2023-09-01 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=456696 --- Comment #5 from P Shao --- Created attachment 161323 --> https://bugs.kde.org/attachment.cgi?id=161323&action=edit updated package list triggering this bug I am attaching the package list which I updated today that introduced this bug on

[kde] [Bug 456696] "QSocketNotifier: Can only be used with threads started with QThread" everywhere

2023-09-01 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=456696 --- Comment #7 from P Shao --- (In reply to P Shao from comment #3) > I ran into exactly the same issue after an upgrade in Arch Linux from > plastma 5.27.6 to 5.27.7 alone with a collection of qt-related upgrade as > well :( Forgot to add

[kde] [Bug 456696] "QSocketNotifier: Can only be used with threads started with QThread" everywhere

2023-09-01 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=456696 --- Comment #8 from P Shao --- (In reply to Fushan Wen from comment #6) > Looks like a problem in Qt. in openSUSE KF was also updated but Qt wasn't, > and I did not encounter the problem. Thanks for sharing the information, any clue what

[kde] [Bug 456696] "QSocketNotifier: Can only be used with threads started with QThread" everywhere

2023-09-03 Thread P Shao
https://bugs.kde.org/show_bug.cgi?id=456696 --- Comment #9 from P Shao --- After some fiddling around through package downgrading/upgrading, I have confirmed at least on my computer it was caused by fcitx5-qt (5.0.17-7 => 5.1.0-1), which makes sense to explain why the bug impacted so m