[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage
https://bugs.kde.org/show_bug.cgi?id=425271 --- Comment #34 from Leandro Lucarella --- (In reply to David Edmundson from comment #32) > We have some logic in xembedsniproxy that says "if our hidden window is > shown, send it to the back again". Clearly someone else is putting our > window back again. Possibly a new kwin change. > > Can you confirm that openbox --replace silences the issue? > Can you also enable any debug in kwin and see if that shows anything? Ah, interesting. I'm using i3, so no kwin for me. I'll try i3 --replace when this happens to see if it changes anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage
https://bugs.kde.org/show_bug.cgi?id=425271 --- Comment #29 from Leandro Lucarella --- For me this happens consistently with BackInTime, usually when it runs after resuming from suspend. When it is doing a backup and the notification area icon is shown, xembedsniproxy uses ~65% CPU (and xorg 100%). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage
https://bugs.kde.org/show_bug.cgi?id=425271 Leandro Lucarella changed: What|Removed |Added CC||luca-...@llucax.com --- Comment #22 from Leandro Lucarella --- I can confirm too. Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-8-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 Leandro Lucarella changed: What|Removed |Added CC||luca-...@llucax.com --- Comment #16 from Leandro Lucarella --- This is bugging me too often. Is very hard for me to see a reason why you wouldn't want to allow suspending, and in any case I think leaving the option to the user to allow reboot and power-off too (even if is burried in some "Advanced" setting somewhere) would make a lot of sense. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 413078] Can't change name of akonadi EWS resource (sort of)
https://bugs.kde.org/show_bug.cgi?id=413078 --- Comment #1 from Leandro Lucarella --- Created attachment 123267 --> https://bugs.kde.org/attachment.cgi?id=123267=edit KMail folder view -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 413078] Can't change name of akonadi EWS resource (sort of)
https://bugs.kde.org/show_bug.cgi?id=413078 --- Comment #3 from Leandro Lucarella --- Created attachment 123269 --> https://bugs.kde.org/attachment.cgi?id=123269=edit KMail akonadi console -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 413078] Can't change name of akonadi EWS resource (sort of)
https://bugs.kde.org/show_bug.cgi?id=413078 --- Comment #2 from Leandro Lucarella --- Created attachment 123268 --> https://bugs.kde.org/attachment.cgi?id=123268=edit KMail accounts view -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 413078] New: Can't change name of akonadi EWS resource (sort of)
https://bugs.kde.org/show_bug.cgi?id=413078 Bug ID: 413078 Summary: Can't change name of akonadi EWS resource (sort of) Product: kdepim Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: leandro.lucare...@quoscient.io Target Milestone: --- Created attachment 123266 --> https://bugs.kde.org/attachment.cgi?id=123266=edit Korganizer SUMMARY When adding an akonadi EWS resource, I change the name of the account to something more meaningful than akonadi_ews_resource_1, but even when in Akonadi Console and KMail settings is shown as expected, in the tree views of KMail, Kontact and KOrganizer it still shows the akonadi_ews_resource_1 name. STEPS TO REPRODUCE 1. Create a new EWS resource/account 2. Rename it to other than the generated default name 3. Open KMail/Korganizer/Kontact OBSERVED RESULT The generated default name is used as the account name/root folder. EXPECTED RESULT The chosen name is used as the account name/root folder. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.62.0 Kernel Version: 5.2.0-3-amd64 OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 23.1 GiB of RAM ADDITIONAL INFORMATION kdepim-runtime 4:18.08.3-4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412830] New: The key sequence 'U' is ambiguous
https://bugs.kde.org/show_bug.cgi?id=412830 Bug ID: 412830 Summary: The key sequence 'U' is ambiguous Product: kmail2 Version: 5.9.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: luca-...@llucax.com Target Milestone: --- SUMMARY Out of the blue, without touching anyting (although it might have been after some upgrade of some KDE component, not KMail), I started to get this message when trying to use the 'U' shortcut to mark messages as unread: The key sequence 'U' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered. I looked in the shortcuts configuration and there is nothing else bound to `U`, not even in the global KDE shortcuts defined in the KDE Settings. STEPS TO REPRODUCE 1. Open KMail 2. Select an e-mail 3. Press the "U" letter in the keyboard OBSERVED RESULT A dialog with this message is shown: The key sequence 'U' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered. EXPECTED RESULT The message is marked as unread. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable, kde version 5:104 (from the debian package) KDE Plasma Version: 5.14.5.1 (?). Is the version of the plasma-desktop package KDE Frameworks Version: ? Qt Version: ? ADDITIONAL INFORMATION If I remove the binding for 'U' from the shortcuts config and then press 'U', there is no visible effect. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392203] Managesieve doesn't work over pure TLS connection
https://bugs.kde.org/show_bug.cgi?id=392203 Leandro Lucarella <luca-...@llucax.com> changed: What|Removed |Added Summary|Managesieve doesn't work|Managesieve doesn't work |over pure TLS connectino|over pure TLS connection -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392203] New: Managesieve doesn't work over pure TLS connectino
https://bugs.kde.org/show_bug.cgi?id=392203 Bug ID: 392203 Summary: Managesieve doesn't work over pure TLS connectino Product: kmail2 Version: 5.6.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sieve Assignee: kdepim-b...@kde.org Reporter: luca-...@llucax.com Target Milestone: --- I couldn't find any way to configure manangesieve over a pure TLS connection (no plain connection + STARTTLS command). There should be a way to configure which type of encrypted channel to use with managesieve. Even when there is no standard port for "sieves", users should be able to configure on it on any custom port. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391806] New: Sieve doesn't error on bad managesieve host
https://bugs.kde.org/show_bug.cgi?id=391806 Bug ID: 391806 Summary: Sieve doesn't error on bad managesieve host Product: kmail2 Version: 5.6.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sieve Assignee: kdepim-b...@kde.org Reporter: luca-...@llucax.com Target Milestone: --- If the configured managesieve host doesn't exist, there is no error reported to the user. When going to Settings -> Manage Sieve Scripts, the progress circle will just go on and on without reporting any errors. A simple typo in the host name is very hard to pin point because of this! -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 73547] sieve will not allow you to retry logging in on a bad password.
https://bugs.kde.org/show_bug.cgi?id=73547 Leandro Lucarella <luca-...@llucax.com> changed: What|Removed |Added CC||luca-...@llucax.com -- You are receiving this mail because: You are watching all bug changes.
