[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 Yosuke Matsumura changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 from Yosuke Matsumura --- (In reply to Zamundaaa from comment #5) > When it happens, can you open the kwin debug console (search for kwin in > krunner) and check the geometry field for the disappeared windows, if > they're offscreen or resized impossibly small, something like that? Hi, I've uploaded screenshots of the Kwin Debug console, opened to the Konsole windows that has disappeared. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 --- Comment #7 from Yosuke Matsumura --- Created attachment 153946 --> https://bugs.kde.org/attachment.cgi?id=153946=edit Kwin Debug Window 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 --- Comment #6 from Yosuke Matsumura --- Created attachment 153945 --> https://bugs.kde.org/attachment.cgi?id=153945=edit Kwin Debug Window 1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 --- Comment #4 from Yosuke Matsumura --- Updated system to following versions; issue still remains: KDE Plasma: 5.26.3 KDE Frameworks: 5.100.0 QT Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 --- Comment #3 from Yosuke Matsumura --- Created attachment 153779 --> https://bugs.kde.org/attachment.cgi?id=153779=edit After screen wake 2 There was a crash report from System Settings, and you can see that other applications that were on screen prior to the screen turning off (Konsole, KWrite) are still running in the Task Manager. However, the window preview is blank, showing the window is gone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 --- Comment #2 from Yosuke Matsumura --- Created attachment 153778 --> https://bugs.kde.org/attachment.cgi?id=153778=edit After screen wake 1 This is what my screen looked like right after waking it. All my windows have disappeared. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 --- Comment #1 from Yosuke Matsumura --- Created attachment 153777 --> https://bugs.kde.org/attachment.cgi?id=153777=edit Screenshot of system before screen turns off I took this screenshot, then waited until the screen turned off -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] New: Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 Bug ID: 461886 Summary: Waking screen causes application windows to disappear Classification: Plasma Product: kwin Version: 5.26.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: yosukematsum...@gmail.com Target Milestone: --- Created attachment 153776 --> https://bugs.kde.org/attachment.cgi?id=153776=edit System log from the timeframe of screen wake SUMMARY This issue occurs after waking the screen after it has turned off (due to Screen Energy Saving) - *not* from Suspend session (when manually putting computer to sleep). Some application windows (though not always all) seem to disappear. The application is still running and its icon is still in the Task Manager. However, clicking the application icon in the Task Manager does not bring the window into view. I end up needing to close the windows from the Task Manager (window preview pane shows blank window as well). Then I can re-launch the application. I see in the system log (attached), that there is this message from the time when I wake the screen: kwin_wayland[14813]: libkwinglutils: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" STEPS TO REPRODUCE 1. In System Settings, Power Management, Energy Saving, enable Screen Energy Saving and set time to some value < Suspend Session time. 2. Wait for screen to turn off as per time set in step 1 3. Wake the screen by pressing key on keyboard OBSERVED RESULT Some windows that were open and visible before the screen turned off - such as Konsole - are no longer visible. However some other windows are unaffected - such as Firefox. I'm unable to find a pattern as to which windows will disappear and which won't, but Konsole seems to be reliably reproducible. EXPECTED RESULT All open and visible windows before the screen turned off should be present when the screen turns back on. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Kinoite 37 (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION GPU: AMD RX 6900XT connected to 4K monitor using DisplayPort -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 442011] kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated
https://bugs.kde.org/show_bug.cgi?id=442011 --- Comment #6 from Yosuke Matsumura --- Sorry, it seems my analysis was mistaken and this patch does not fix the "findInCache with a lastModified timestamp of 0 is deprecated" message, but does fix usability of Kinoite when set to UTC timezone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442011] kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated
https://bugs.kde.org/show_bug.cgi?id=442011 Yosuke Matsumura changed: What|Removed |Added CC||yosukematsum...@gmail.com --- Comment #3 from Yosuke Matsumura --- I think I've found the root cause (https://discussion.fedoraproject.org/t/kinoite-installation-with-utc-timezone-breaks-kde/34293/8?u=guiltydoggy). I think a change to the updateHash (https://github.com/KDE/kservice/blob/master/src/sycoca/kbuildsycoca.cpp#L610) to add 1 so that the hash no longer equals 0 may fix the problem, but I don't know what other impacts it may have: hash += fi.lastModified().toSecsSinceEpoch(); -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449159] Cannot log in to Wayland session
https://bugs.kde.org/show_bug.cgi?id=449159 Yosuke Matsumura changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #6 from Yosuke Matsumura --- Upon further investigation, I believe this is an SELinux issue. Closing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449159] Cannot log in to Wayland session
https://bugs.kde.org/show_bug.cgi?id=449159 --- Comment #5 from Yosuke Matsumura --- Created attachment 145954 --> https://bugs.kde.org/attachment.cgi?id=145954=edit Full boot log Attached is a full log of a failed login. I’ve compared the logs for a successful login (using the old deployment) to a failed one (new deployment, attached). In the new deployment, I am seeing these errors: fedora-pc systemd-user-runtime-dir[1430]: Failed to mount per-user tmpfs directory /run/user/978: No such file or directory fedora-pc sddm-helper[1428]: pam_systemd(sddm-greeter:session): Failed to stat() runtime directory ‘/run/user/978’: No such file or directory Whereas in a successful login, these don’t appear. Using a different TTY upon getting to the login screen, I can `ls -l /run/user` and indeed when booted in the new deployment , /run/user/ is empty. When booted in the old (working) deployment I see 2 entries in /run/user/ - one for sddm, and one for my username. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449159] Cannot log in to Wayland session
https://bugs.kde.org/show_bug.cgi?id=449159
--- Comment #4 from Yosuke Matsumura ---
(In reply to Vlad Zahorodnii from comment #3)
> Do you use SDDM? If not, make sure that environment variables such as
> XDG_RUNTIME_DIR are set
I use SDDM.
yosuke@fedora-pc ~ systemctl status sddm
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor
preset: enabled)
Active: active (running) since Wed 2022-01-26 06:38:08 CST; 1min 26s ago
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 1395 (sddm)
Tasks: 33 (limit: 38323)
Memory: 199.5M
CPU: 248ms
CGroup: /system.slice/sddm.service
├─1395 /usr/bin/sddm
└─1406 /usr/libexec/Xorg -dpi 0 -auth
/var/run/sddm/{fb1fdb8a-fcaf-4ef0-9522-dffa4f269a7f} -background none -noreset
-displayfd 16 -seat>
Jan 26 06:38:14 fedora-pc sddm-helper[1532]: gkr-pam: unable to locate daemon
control file
Jan 26 06:38:14 fedora-pc sddm-helper[1532]: gkr-pam: stashed password to try
later in open session
Jan 26 06:38:14 fedora-pc sddm-helper[1532]: pam_kwallet5(sddm:auth):
pam_kwallet5: pam_sm_authenticate
Jan 26 06:38:14 fedora-pc sddm-helper[1532]: pam_kwallet5(sddm:setcred):
pam_kwallet5: pam_sm_setcred
Jan 26 06:38:14 fedora-pc sddm-helper[1532]: pam_unix(sddm:session): session
opened for user yosuke(uid=1000) by (uid=0)
Jan 26 06:38:14 fedora-pc sddm-helper[1532]: gkr-pam: gnome-keyring-daemon
started properly and unlocked keyring
Jan 26 06:38:14 fedora-pc sddm-helper[1532]: pam_kwallet5(sddm:session):
pam_kwallet5: pam_sm_open_session
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 449159] Cannot log in to Wayland session
https://bugs.kde.org/show_bug.cgi?id=449159 --- Comment #2 from Yosuke Matsumura --- (In reply to Vlad Zahorodnii from comment #1) > Can you attach ~/.local/share/sddm/wayland-session.log to the bug report > please? I don't seem to have that directory and log. yosuke@fedora-pc ~/.local/share ls -l drwx--@- yosuke 21 Sep 2021 applications drwxr-xr-x@- yosuke 25 Sep 2021 aurorae drwxr-xr-x@- yosuke 25 Jan 09:57 baloo drwxr-xr-x@- yosuke 26 Oct 2021 color-schemes drwx--@- yosuke 31 Aug 2021 containers drwx--@- yosuke 31 Aug 2021 desktop-directories drwxr-xr-x@- yosuke 7 Oct 2021 discover drwxr-xr-x@- yosuke 17 Sep 2021 dolphin drwx--@- yosuke 31 Aug 2021 evolution drwx--@- yosuke 25 Jan 08:28 flatpak drwxr-xr-x@- yosuke 16 Sep 2021 fonts drwxr-xr-x@- yosuke 31 Aug 2021 gnome-settings-daemon drwx--@- yosuke 17 Sep 2021 gnome-shell drwx--@- yosuke 17 Sep 2021 gvfs-metadata drwxr-xr-x@- yosuke 31 Aug 2021 ibus-typing-booster drwxr-xr-x@- yosuke 31 Aug 2021 icc drwx--@- yosuke 3 Dec 2021 icons drwxr-xr-x@- yosuke 17 Sep 2021 kactivitymanagerd drwxr-xr-x@- yosuke 25 Jan 10:00 kcookiejar drwxr-xr-x@- yosuke 17 Sep 2021 kded5 drwxr-xr-x@- yosuke 25 Jan 10:01 keyrings drwxr-xr-x@- yosuke 17 Sep 2021 khelpcenter drwxr-xr-x@- yosuke 25 Jan 10:07 klipper drwxr-xr-x@- yosuke 18 Oct 2021 knewstuff3 drwxr-xr-x@- yosuke 18 Oct 2021 konsole .rw---@ 5.6k yosuke 25 Jan 10:01 krunnerstaterc drwxr-xr-x@- yosuke 28 Sep 2021 kscreen drwxr-xr-x@- yosuke 26 Oct 2021 kwalletd drwxr-xr-x@- yosuke 6 Oct 2021 kwrite drwxr-xr-x@- yosuke 13 Oct 2021 kxmlgui5 drwxr-xr-x@- yosuke 12 Oct 2021 lutris drwx--@- yosuke 14 Oct 2021 mc drwxr-xr-x@- yosuke 31 Aug 2021 nautilus drwxr-xr-x@- yosuke 20 Oct 2021 okular drwxr-@- yosuke 31 Aug 2021 pki drwxr-xr-x@- yosuke 25 Sep 2021 plasma drwxr-xr-x@- yosuke 21 Oct 2021 plasma-systemmonitor drwxr-xr-x@- yosuke 12 Oct 2021 plasma-vault drwxr-xr-x@- yosuke 17 Sep 2021 plasma_icons drwxr-xr-x@- yosuke 7 Oct 2021 plasmashell drwxr-xr-x@- yosuke 25 Jan 09:46 RecentDocuments .rw---@ 27k yosuke 3 Nov 2021 recently-used.xbel drwxr-xr-x@- yosuke 17 Sep 2021 remoteview drwx--@- yosuke 31 Aug 2021 sounds drwx--@- yosuke 23 Nov 2021 Trash .rw-r--r--@ 11k yosuke 14 Oct 2021 user-places.xbel .rw-r--r--@ 11k yosuke 14 Oct 2021 user-places.xbel.bak .rw-r--r--@0 yosuke 14 Oct 2021 user-places.xbel.tbcache drwxr-xr-x@- yosuke 16 Sep 2021 virtualenv drwxr-xr-x@- yosuke 12 Oct 2021 webkitgtk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449159] New: Cannot log in to Wayland session
https://bugs.kde.org/show_bug.cgi?id=449159 Bug ID: 449159 Summary: Cannot log in to Wayland session Product: kwin Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: yosukematsum...@gmail.com Target Milestone: --- Created attachment 145923 --> https://bugs.kde.org/attachment.cgi?id=145923=edit Journalctl error: kwin_wayland_wrapper SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Boot 2. Select Wayland on login screen 3. Enter password and hit Enter OBSERVED RESULT One of two outcomes: 1) Screen momentarily goes black, then the login screen re-appears. 2) Screen permanently goes black, the signal to the monitor is lost. EXPECTED RESULT Log in to Wayland session SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.23.4 (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I am using and AMD GPU, using the amdgpu drivers. This occurred sometime after January 12, 2022. I am running Fedora Kinoite. Using a previous deployment from Jan 12, I do not have this issue. The working deployment from Jan 12 is running the same KDE Plasma and Frameworks versions as the current (broken) deployment. Only notable differences are: Kernel 5.15.13-200.fc35 -> 5.15.16-200.fc35 mesa 21.3.3-1.fc35 -> 21.3.4-3.fc35 Attached is a journalctl entry from a time when the login screen turned black and returned to the login screen. There seems to have been a crash with the kwin_wayland_wrapper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445602] Application menu item changes depending on which way (top/bottom) a submenu is accessed
https://bugs.kde.org/show_bug.cgi?id=445602 Yosuke Matsumura changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Yosuke Matsumura --- (In reply to Nate Graham from comment #3) > That's extremely odd. I can't get it to happen with any of my categories on > Fedora 34. Thanks for the reply. This reminded me to re-check this bug. Just tested again and it seems to be fixed. Got an update to Frameworks 5.88 a day or two ago, unsure if that is related. In either case, closing this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445602] Application menu item changes depending on which way (top/bottom) a submenu is accessed
https://bugs.kde.org/show_bug.cgi?id=445602 --- Comment #2 from Yosuke Matsumura --- Workaround: Changing the Application Launcher settings for "Show other applications" from "In a list" to "In a grid" fixes the problem. Looks like the issue only presents itself when set to "In a list". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445602] Application menu item changes depending on which way (top/bottom) a submenu is accessed
https://bugs.kde.org/show_bug.cgi?id=445602 --- Comment #1 from Yosuke Matsumura --- Created attachment 143637 --> https://bugs.kde.org/attachment.cgi?id=143637=edit Screenshot of Menu Editor This is what the configuration for the Application Launcher menu looks like. FileZilla is not even in the Administration category - it is filed under Internet. And it shows up properly in that submenu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443752] Dolphin Closed Unexpectedly if Terminal Panel is open
https://bugs.kde.org/show_bug.cgi?id=443752 Yosuke Matsumura changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Yosuke Matsumura --- Revisiting this after update to Plasma 5.23.2 Seems that the issue is no longer manifesting. Closing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445602] New: Application menu item changes depending on which way (top/bottom) a submenu is accessed
https://bugs.kde.org/show_bug.cgi?id=445602 Bug ID: 445602 Summary: Application menu item changes depending on which way (top/bottom) a submenu is accessed Product: plasmashell Version: 5.23.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: yosukematsum...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 143636 --> https://bugs.kde.org/attachment.cgi?id=143636=edit Video of the observed bug SUMMARY Running Fedora 35 Kinoite. Just got updated to Plasma 5.23.2 from 5.22 today. Noticed this odd issue with the menu item under the "Administration" submenu in the Application Launcher. When moving the mouse from the top (All Applications -> Administration), the application shown is FileZilla. When moving the mouse from the bottom (Development -> Administration), the application shown is Firewall. Video of bug is attached. Restarting plasmashell has no effect. STEPS TO REPRODUCE 1. Have Application Launcher set. 2. Access "Administration" submenu from top or bottom. 3. OBSERVED RESULT Application listed in the Administration submenu changes depending on which way the submenu is accessed. EXPECTED RESULT Consistent listing of application. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 35 Kinoite (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION - Plasma Wayland session -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444801] Turning monitor off and back on causes plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=444801 Yosuke Matsumura changed: What|Removed |Added CC||yosukematsum...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443753] New: Tool tips background shading/color does not match tool tip size
https://bugs.kde.org/show_bug.cgi?id=443753 Bug ID: 443753 Summary: Tool tips background shading/color does not match tool tip size Product: plasmashell Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: yosukematsum...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142452 --> https://bugs.kde.org/attachment.cgi?id=142452=edit Video of the observed bug SUMMARY Tool tips show incorrect background shading/transparency when moving from one icon to another. STEPS TO REPRODUCE 1. Enable Tool Tips for Icon Only Task Manager in panel 2. Hover over an application icon, and move cursor to another icon 3. OBSERVED RESULT Background/transparency of tool tip is incorrectly rendered for the tool tip pop-ups. See attached video. EXPECTED RESULT Consistent shading for the entire tool tip pop up. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 35 Kinoite (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Plasma Wayland session -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443752] New: Dolphin Closed Unexpectedly if Terminal Panel is open
https://bugs.kde.org/show_bug.cgi?id=443752 Bug ID: 443752 Summary: Dolphin Closed Unexpectedly if Terminal Panel is open Product: dolphin Version: 21.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: yosukematsum...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When Dolphin is configured to have the Terminal panel open, it almost always closes with a "Dolphin Closed Unexpectedly" notification when the Dolphin window is closed by clicking the "X" close window button. STEPS TO REPRODUCE 1. Open Dolphin, and set Show Panels > Terminal 2. Close Dolphin window by clicking the "X" button in the window title bar 3. OBSERVED RESULT Notification (Dr Konqi) pops up saying Dolphin Closed Unexpectedly. EXPECTED RESULT No error message/crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 35 Kinoite (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION - Plasma Wayland session Launched Dolphin from Konsole to see if there were any messages in stdout. Only output was: KCrash: Application 'dolphin' crashing... KCrash: Attempting to start /usr/libexec/drkonqi org.kde.drkonqi: Unable to find an internal debugger that can work with the KCrash backend -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439815] Window randomly become transparent, when close ghost image remains
https://bugs.kde.org/show_bug.cgi?id=439815 Yosuke Matsumura changed: What|Removed |Added CC||yosukematsum...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443027] Screen elements are reset after screen is turned off and on
https://bugs.kde.org/show_bug.cgi?id=443027 Yosuke Matsumura changed: What|Removed |Added Version|5.22.4 |5.22.5 Product|KScreen |plasmashell Assignee|kscreen-bugs-n...@kde.org |plasma-b...@kde.org Component|common |generic-crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420160] Plasma crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Yosuke Matsumura changed: What|Removed |Added CC||yosukematsum...@gmail.com --- Comment #60 from Yosuke Matsumura --- *** Bug 443027 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 443027] Screen elements are reset after screen is turned off and on
https://bugs.kde.org/show_bug.cgi?id=443027 Yosuke Matsumura changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #11 from Yosuke Matsumura --- This looks to be a duplicate of 420160. Closing. *** This bug has been marked as a duplicate of bug 420160 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420160] Plasma crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Yosuke Matsumura changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=443027 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 443027] Screen elements are reset after screen is turned off and on
https://bugs.kde.org/show_bug.cgi?id=443027 Yosuke Matsumura changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=420160 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 443027] Screen elements are reset after screen is turned off and on
https://bugs.kde.org/show_bug.cgi?id=443027 --- Comment #10 from Yosuke Matsumura --- (In reply to Nate Graham from comment #9) > Seems like the system is detecting your screen as a newly-connected screen, > rather than the same one. This triggers various multi-screen bugs in Plasma > such as Bug 356225, Bug 356727, Bug 391531, and Bug 436648. > > Let's focus on the issue with your waking-up monitor being mis-detected as a > new screen here, as fixing that will no longer expose you to those Plasma > bugs. > > You're using an AMD GPU, right? If so, this is most likely > https://bugzilla.kernel.org/show_bug.cgi?id=206387, which triggers those > Plasma bugs. I just switched the connection to my monitor from DisplayPort to HDMI (no DP ports connected to the GPU). This same issue manifests. That amdgpu bug seems to be specific to DisplayPort, unless I'm mistaken, so it would seem that it might not be the root cause. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443027] Screen elements are reset after screen is turned off and on
https://bugs.kde.org/show_bug.cgi?id=443027 --- Comment #8 from Yosuke Matsumura --- Created attachment 141965 --> https://bugs.kde.org/attachment.cgi?id=141965=edit Settings - Display Configuration - Reloaded Looking at the Display Configuration screen in System Settings after turning the screen back on, there is a new message saying: "A new output has been added. Settings have been reloaded." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443027] Screen elements are reset after screen is turned off and on
https://bugs.kde.org/show_bug.cgi?id=443027 --- Comment #7 from Yosuke Matsumura --- (In reply to Nate Graham from comment #6) > How many screens do you have? 1, or more than 1? Just 1 screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443027] Screen elements are reset after screen is turned off and on
https://bugs.kde.org/show_bug.cgi?id=443027 Yosuke Matsumura changed: What|Removed |Added Summary|Screen elements are reset |Screen elements are reset |after screen wakes from off |after screen is turned off ||and on -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443027] Screen elements are reset after screen wakes from off
https://bugs.kde.org/show_bug.cgi?id=443027 --- Comment #5 from Yosuke Matsumura --- Created attachment 141963 --> https://bugs.kde.org/attachment.cgi?id=141963=edit User journalctl journalctl --user -S 2021-09-2713:17:10 -U 2021-09-2713:18:18 > User_Journal.txt -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443027] Screen elements are reset after screen wakes from off
https://bugs.kde.org/show_bug.cgi?id=443027 --- Comment #4 from Yosuke Matsumura --- Created attachment 141962 --> https://bugs.kde.org/attachment.cgi?id=141962=edit System journalctl journalctl --system -S 2021-09-2713:17:10 -U 2021-09-2713:18:18 > User_Journal.txt -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443027] Screen elements are reset after screen wakes from off
https://bugs.kde.org/show_bug.cgi?id=443027 --- Comment #3 from Yosuke Matsumura --- Comment on attachment 141960 --> https://bugs.kde.org/attachment.cgi?id=141960 What the screen looks like monitor is turned off What it looks like *before* the monitor is turned off -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443027] Screen elements are reset after screen wakes from off
https://bugs.kde.org/show_bug.cgi?id=443027 --- Comment #2 from Yosuke Matsumura --- Created attachment 141961 --> https://bugs.kde.org/attachment.cgi?id=141961=edit What the screen looks like after monitor is turned back on -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443027] Screen elements are reset after screen wakes from off
https://bugs.kde.org/show_bug.cgi?id=443027 --- Comment #1 from Yosuke Matsumura --- Created attachment 141960 --> https://bugs.kde.org/attachment.cgi?id=141960=edit What the screen looks like monitor is turned off -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443027] New: Screen elements are reset after screen wakes from off
https://bugs.kde.org/show_bug.cgi?id=443027 Bug ID: 443027 Summary: Screen elements are reset after screen wakes from off Product: kwin Version: 5.22.5 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: yosukematsum...@gmail.com Target Milestone: --- SUMMARY Desktop computer's monitor/screen turns off (either manually, or due to sleep timer). When the screen is turned back on, the desktop is "reset" - Panel has disappeared, desktop wallpaper reset to default, and existing windows are moved/resized. STEPS TO REPRODUCE 1. Boot up & Log in (Wayland session) - does not reproduce in X11. 2. Turn off the screen. Note - just the screen power needs to be turned off. Does not require computer to go into suspend mode. Can be done in multiple ways - all produce the error: a. In System Settings > Power Management > Energy Savings > Button Events Handling > Set When power button is pressed "Turn off screen". And then press the power button on the computer. b. Press the power button on the monitor (or pull the power cord to the monitor). c. Wait for system to sleep and causing monitor to power off. 3. Wait 30s (I haven't determined a minimum time required, but sometimes it doesn't happen if the screen is turned back on quickly after turning off). OBSERVED RESULT Screen is "reset". The side panel (only panel) is gone. The desktop background/wallpaper is set to default. The open window is moved to upper left and resized. See attachment: After Screen On.png EXPECTED RESULT Screen should appear exactly the same as before the screen is turned off. See attachment: Before Screen Off.png SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 35 Kinoite (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION GPU is Navi 21/6900XT Mesa 21.2.2 Logs attached. Screen Off at 13:17:15. Screen On at 13:18:00. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442804] Keyboard layout not remembered after logout
https://bugs.kde.org/show_bug.cgi?id=442804 Yosuke Matsumura changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442804] Keyboard layout not remembered after logout
https://bugs.kde.org/show_bug.cgi?id=442804 --- Comment #4 from Yosuke Matsumura --- (In reply to Andrey from comment #3) > Then, please note the comment above. Thanks. It seems that setting session restore 'on' does maintain the setting. I prefer to not have to restore a session, and that's not the same behavior as X11, but I'll accept that if it is the intended solution. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442804] Keyboard layout not remembered after logout
https://bugs.kde.org/show_bug.cgi?id=442804 --- Comment #2 from Yosuke Matsumura --- Sorry, I should have mentioned it in the original report. It only occurs in Wayland. The layout is preserved as expected in X11. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442804] New: Keyboard layout not remembered after logout
https://bugs.kde.org/show_bug.cgi?id=442804 Bug ID: 442804 Summary: Keyboard layout not remembered after logout Product: systemsettings Version: 5.22.4 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: yosukematsum...@gmail.com CC: butir...@gmail.com Target Milestone: --- SUMMARY Same as bug 412101, which is marked resolved with a fix in 5.20. However, I am experiencing the same bug in 5.22.4. https://bugs.kde.org/show_bug.cgi?id=412101 STEPS TO REPRODUCE 1. Set up 2 keyboard layouts (set to Global switching policy). 2. Select the non-primary layout using the keyboard layout tray icon. 3. Log out. 4. Log in. OBSERVED RESULT The primary layout is selected upon login. EXPECTED RESULT The last selected layout (in this case, the non-primary), to be selected upon login. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 35 Kinoite (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
