[plasma-browser-integration] [Bug 413286] New: plasma-browser-integration-host process at 100%CPU (on one core) when chromium started in another user's plasma session (via kdesu)
https://bugs.kde.org/show_bug.cgi?id=413286 Bug ID: 413286 Summary: plasma-browser-integration-host process at 100%CPU (on one core) when chromium started in another user's plasma session (via kdesu) Product: plasma-browser-integration Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: m...@patrick-hanft.de Target Milestone: --- On my work computer I use my company account (using LDAP/Samba) to start my plasma session in a work context. However, I sometimes want to be able to look at websites from a personal context. That's why I do have a regular local user account, which I use for personal stuff. The chromium instance that is installed there is also synced with my chromium instance on my home computer via Google account. Therefore, also the support for plasma-browser-integration is active in this instance. But usually I do not start a second X session with my personal account, but I do start chromium using `kdesu -u chromium`. In this case, a process called `plasma-browser-integration-host` ist started with my personal account user, which has not started the X session. And this process continuesly reaches 100% cpu time on a single core. I assume, this is due to the fact, that it probably doesn't have the right to talk to other graphical processes. STEPS TO REPRODUCE 1. Have two users 2. Start plasma session with first user 3. Start chromium as second user using `kdesu -u seconduser chromium` OBSERVED RESULT Have `plasma-browser-integration-host` process, consuming high cpu on single core. EXPECTED RESULT If I still have a `plasma-browser-integration-host` process running as seconduser, it should not consume high cpu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 379003] Wallpaper "Picture of the Day" from National Geographics only changing after reboot or not at all.
https://bugs.kde.org/show_bug.cgi?id=379003 Patrick Hanft <m...@patrick-hanft.de> changed: What|Removed |Added CC||m...@patrick-hanft.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370003] Performance issues (laggy animations, stuttering keyboard input handling, severe frame drops in videos) after using plasmashell for a few days
https://bugs.kde.org/show_bug.cgi?id=370003 Patrick Hanft <m...@patrick-hanft.de> changed: What|Removed |Added CC||m...@patrick-hanft.de -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 365812] global "lock screen" shortcut unaware of user's keyboard layout
https://bugs.kde.org/show_bug.cgi?id=365812 Patrick Hanft <m...@patrick-hanft.de> changed: What|Removed |Added CC||m...@patrick-hanft.de -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 365812] New: global "lock screen" shortcut unaware of user's keyboard layout
https://bugs.kde.org/show_bug.cgi?id=365812 Bug ID: 365812 Summary: global "lock screen" shortcut unaware of user's keyboard layout Product: ksmserver Version: 5.7.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: m...@patrick-hanft.de I'm a user of the alternative keyboard layout "Neo 2" which is an alternative keyboard layout optimized for German language. Usually this is very vell supported althrough the plasma desktop. Beginning with my upgrade to plasma 5 coming from KDE 4.x, the global "lock screen shortcut" stopped working for me. While all other shortcuts worked quite normally, both, the default [Ctrl]+[Alt]+[L] as well as any other configured variant ([Win]+[L] and others) did not work as expected. By pure accident I recently I realized, that this shortcut probably does not respect my user keyboard layout, as I suddenly locked my screen by hitting [Ctrl]+[Alt]+[T] instead. To help visualize this issue, please find Neo 2 keyboard layout here: https://en.wikipedia.org/wiki/Keyboard_layout#/media/File:Neo_2.0-Tastaturbelegung_Ebene1.svg Reproducible: Always Steps to Reproduce: 1. configure de-neo2 as user's keyboard layout 2. press [Ctrl]+[Alt]+[L] in neo2 layout (which maps to physical [Ctrl]+[Alt]+[E] in qwerty/qwertz layout) Actual Results: nothing happens Expected Results: screen should bo locked 3. instead when you press [Ctrl]+[Alt]+[T] in neo2 layout – which maps to [Ctrl]+[Alt]+[L] in usual Qwerty/Qwertz layout – result: screen locks. -- You are receiving this mail because: You are watching all bug changes.
