[kmail2] [Bug 483656] icon in kde systray, no effect
https://bugs.kde.org/show_bug.cgi?id=483656 aeris changed: What|Removed |Added CC||ae...@imirhil.fr --- Comment #4 from aeris --- Reproducible here too since kde 5 -> kde 6 migration Arch Linux, kmail 24.02.0-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384702] KWin doesn't expose a way to use one keymap per keyboard
https://bugs.kde.org/show_bug.cgi?id=384702 aeris changed: What|Removed |Added CC||ae...@imirhil.fr --- Comment #3 from aeris --- Hello, I bump this bug after 5 years, because I'm hitting it on KDE 5 Wayland. Same here, I'm using FR-BEPO layout for my main keyboard (Moonlander), but have a secondary Typematrix keyboard and I need to use US for Yubikey (physically hardcoded to send US keycode). So my X11 config is: ``` Section "InputClass" Identifier "default" MatchIsKeyboard "yes" Option "XkbModel""pc105" Option "XkbLayout" "fr" Option "XkbVariant" "bepo" Option "XkbOptions" "kpdl:kposs,grp:sclk_toggle,compose:lwin" EndSection Section "InputClass" Identifier "typematrix" MatchIsKeyboard "yes" MatchVendor "TypeMatrix.com" Option "XkbModel" "tm2030USB-102" Option "XkbLayout" "fr" Option "XkbVariant" "bepo" Option "XkbOptions" "kpdl:kposs,grp:sclk_toggle,compose:lwin" EndSection Section "InputClass" Identifier "moonlander" MatchIsKeyboard "yes" MatchVendor "ZSA" Option "XkbModel" "pc105" Option "XkbLayout" "fr" Option "XkbVariant" "bepo" EndSection Section "InputClass" Identifier "yubikey" MatchIsKeyboard "yes" MatchVendor "Yubico" Option "XkbModel" "pc105" Option "XkbLayout" "us" Option "XkbVariant" "basic" EndSection ``` Currently Wayland is broken because only one layout is possible, and so I can't have the correct keyboard model (tm2030USB-102 / pc105) or layout (FR-BEPO / US / FR) based on the related physical keyboard. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418217] background setting is not retained
https://bugs.kde.org/show_bug.cgi?id=418217 --- Comment #16 from aeris --- The "seems working" version doesn't work too… Black screen at restart. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418217] background setting is not retained
https://bugs.kde.org/show_bug.cgi?id=418217 --- Comment #13 from aeris --- Created attachment 126713 --> https://bugs.kde.org/attachment.cgi?id=126713=edit Bugged config -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418217] background setting is not retained
https://bugs.kde.org/show_bug.cgi?id=418217 --- Comment #14 from aeris --- Both config enclosed :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418217] background setting is not retained
https://bugs.kde.org/show_bug.cgi?id=418217 --- Comment #12 from aeris --- Created attachment 126712 --> https://bugs.kde.org/attachment.cgi?id=126712=edit Seems working config -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418217] background setting is not retained
https://bugs.kde.org/show_bug.cgi?id=418217 --- Comment #6 from aeris --- Tested with Haenau, same behavior, settings seems ok when validating, but black screen after logout/login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418217] background setting is not retained
https://bugs.kde.org/show_bug.cgi?id=418217 aeris changed: What|Removed |Added CC||ae...@imirhil.fr --- Comment #4 from aeris --- Same behavior here. Settings wallpaper seems ok when you validate your settings (image correctly displayed), but restarting let the wallpaper black. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 --- Comment #24 from aeris --- Ok, here is the root cause: https://github.com/KDE/libksieve/blob/master/src/kmanagesieve/session.cpp#L171 With CRAM-MD5, the challenge is on the `response.key()`, not on the `data` field, which is here empty. Don't know how to fix this without breaking other auth type… -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 --- Comment #23 from aeris --- Trouble is here: https://github.com/KDE/libksieve/blob/master/src/kmanagesieve/sessionthread.cpp#L265-L266 Seems strange, the challenge is expected to be read *before* the AUTHENTICATE command… -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 --- Comment #22 from aeris --- Seems the used challenge is empty string ./gen-auth.pl CRAM-MD5 "aeris" "$PASS" "" YWVyaXMgMTliMTYxYjNkMGI4YWY3OGRlNjkwNDFkNWQ4Zm= Which is the same as the always sent token in my case -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 aeris changed: What|Removed |Added CC||ae...@imirhil.fr --- Comment #21 from aeris --- Same here. When debugging, I notice the returned CRAM-MD5 is always the same, whatever the challenge the server send. Aug 15 10:10:49 kamino dovecot[25805]: auth: Debug: client passdb out: CONT 1PDE2MzYzMDkzMDA4MTM5MTYuMTU2NTg2Mzg0OUBrYW1pbm8+ Aug 15 10:10:49 kamino dovecot[25805]: auth: Debug: client in: CONT1 YWVyaXMgMTliMTYxYjNkMGI4YWY3OGRlNjkwNDFkNWQ4Zm= (previous base64 data may contain sensitive data) Aug 15 10:11:00 kamino dovecot[25805]: auth: Debug: client passdb out: CONT 1PDU3NjA0MjQyNTkyMzAwMzEuMTU2NTg2Mzg2MEBrYW1pbm8+ Aug 15 10:11:00 kamino dovecot[25805]: auth: Debug: client in: CONT1 YWVyaXMgMTliMTYxYjNkMGI4YWY3OGRlNjkwNDFkNWQ4Zm= (previous base64 data may contain sensitive data) Notice the 2 challenges PDE2MzYzMDkzMDA4MTM5MTYuMTU2NTg2Mzg0OUBrYW1pbm8+ and PDU3NjA0MjQyNTkyMzAwMzEuMTU2NTg2Mzg2MEBrYW1pbm8+, but the same response YWVyaXMgMTliMTYxYjNkMGI4YWY3OGRlNjkwNDFkNWQ4Zm -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404700] Unable to select GPG key not matching identity email
https://bugs.kde.org/show_bug.cgi?id=404700 aeris changed: What|Removed |Added Version|unspecified |5.11.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404700] Unable to select GPG key not matching identity email
https://bugs.kde.org/show_bug.cgi?id=404700 aeris changed: What|Removed |Added Component|crypto |config dialog --- Comment #1 from aeris --- Perhaps this is related to https://bugs.kde.org/show_bug.cgi?id=406909 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406909] Unable to select GPG key with a + in address
https://bugs.kde.org/show_bug.cgi?id=406909 --- Comment #2 from aeris --- Created attachment 119644 --> https://bugs.kde.org/attachment.cgi?id=119644=edit Address configured on identity -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406909] Unable to select GPG key with a + in address
https://bugs.kde.org/show_bug.cgi?id=406909 --- Comment #3 from aeris --- Created attachment 119645 --> https://bugs.kde.org/attachment.cgi?id=119645=edit No GPG key available -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406909] Unable to select GPG key with a + in address
https://bugs.kde.org/show_bug.cgi?id=406909 --- Comment #1 from aeris --- Created attachment 119643 --> https://bugs.kde.org/attachment.cgi?id=119643=edit GPG show the corresponding key -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406909] New: Unable to select GPG key with a + in address
https://bugs.kde.org/show_bug.cgi?id=406909 Bug ID: 406909 Summary: Unable to select GPG key with a + in address Product: kmail2 Version: 5.11.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: ae...@imirhil.fr Target Milestone: --- SUMMARY When using an email address with a "+" on it, kmail doesn't detect any GPG key even if at least one has a matching UID STEPS TO REPRODUCE 1. Create a GPG key with an UID containing an address containing a "+" 2. Create a Kmail identity using this address 3. Select a GPG key for this Kmail identity OBSERVED RESULT No GPG key show on dropdown list EXPECTED RESULT GPG key available on dropdown list SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.15.4-1 KDE Frameworks Version: KDE Frameworks 5.57.0 Qt Version: Qt 5.12.3 (built on 5.12.2) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404700] New: Unable to select GPG key not matching identity email
https://bugs.kde.org/show_bug.cgi?id=404700 Bug ID: 404700 Summary: Unable to select GPG key not matching identity email Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: ae...@imirhil.fr Target Milestone: --- Previously (version unknown, will try to find a working one later), when creating a kmail identity, you can choose a GPG key not matching your email identity. This is useful at least for alias identity using a foo+...@example.org email address but a f...@example.org GPG identity. In new version (18.12.2-1 arch package), the GPG key drop-down only selects GPG key with a identity matching the given email, and no entry to manually select another key. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 --- Comment #32 from aeris --- Same trouble here Enclosed to this ticker a feed which generate bugged entries after a "refresh feed" action. Seem broken entries matches the one with the bugged date, only the 5 last entries are correctly displayed. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 --- Comment #31 from aeris --- Created attachment 114664 --> https://bugs.kde.org/attachment.cgi?id=114664=edit Broken entries after refresh from bugged feed -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 --- Comment #30 from aeris --- Created attachment 114663 --> https://bugs.kde.org/attachment.cgi?id=114663=edit Bad date on some entries -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 aeris changed: What|Removed |Added CC||ae...@imirhil.fr --- Comment #29 from aeris --- Created attachment 114662 --> https://bugs.kde.org/attachment.cgi?id=114662=edit bugged feed Dump of http://blog.xebia.fr/feed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365450] Using the "type to search..." feature on the K menu (application launcher/"start menu") doesn't produce results
https://bugs.kde.org/show_bug.cgi?id=365450 --- Comment #2 from aeris <ae...@imirhil.fr> --- After some more web search, seems upgrading libkf5plasma5 to sid (from 5.22.0-1 to 5.23.0-1), no more trouble. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829614#55 -- You are receiving this mail because: You are watching all bug changes.
