[ktorrent] [Bug 459271] KTorrent crash frequently
https://bugs.kde.org/show_bug.cgi?id=459271 Lukáš Turek <8...@8an.cz> changed: What|Removed |Added CC||8...@8an.cz --- Comment #1 from Lukáš Turek <8...@8an.cz> --- I had the same problem and managed to fix it by raising the hard limit of the number of open files from 4096 to 16384. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #52 from Lukáš Turek <8...@8an.cz> --- (In reply to Albert Vaca from comment #43) > I've modified GSConnect to use ECDSA and it doesn't seem to fix the issue. > Here's my change: > https://github.com/albertvaka/gnome-shell-extension-gsconnect/compare/main... > ecdsa-keys > > After applying this change I deleted ~/.config/gsconnect to force it to > recreate a key. I tried to replace RSA certficate in KDE Connect with ECDSA, but it didn't work either. I used this command to generate it: openssl req -new -x509 -set_serial 10 -sha512 -newkey ec -pkeyopt ec_paramgen_curve:prime256v1 -nodes -keyout privateKey.pem -days 3650 -out certificate.pem -subj "/CN=_3e4db661_39a2_4d04_bd59_e6c962f356a2_/O=KDE/OU=Kde connect" Unfortunately, kdeconnectd refuses the new private key: kdeconnect.core: Private key from "/home/8an/.config/kdeconnect/privateKey.pem" is not valid -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #42 from Lukáš Turek <8...@8an.cz> --- Unfortunately you're right, it didn't help, it really seems the RFC8308 extension is needed, which requires MINA SSHD version 2.3.0 or later. Do we really need to use RSA for client authentication? Or could the KDE Connect client (Linux app) also switch to an ECDSA key? The error "no mutual signature algorithm" does not appear when I try to send my ECDSA public key: debug1: Next authentication method: publickey debug1: Offering public key: id_rsa RSA SHA256:En18wk81oylB2/tXALRVR665pvuP3XHZOVUdTWnZ06w agent debug1: send_pubkey_test: no mutual signature algorithm debug1: Offering public key: id_ecdsa ECDSA SHA256:JL1U9qfHt51GmmiT41JB9WDRDP4cWWA8H/boCR08qCU explicit debug2: we sent a publickey packet, wait for reply -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #39 from Lukáš Turek <8...@8an.cz> --- I tried that, but it made no difference. It seems that key exchange algorithms are something different, what's missing is signature algorithm "rsa-sha2-256" and some protocol extension. These additional lines are in SSH output when I connect to a Linux server using my RSA key: debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= The extension should be supported in MINA SSHD: https://issues.apache.org/jira/browse/SSHD-895 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #37 from Lukáš Turek <8...@8an.cz> --- I cleared KDE Connect settings on my phone, and it generated an ECDSA key instead of RSA, so option HostKeyAlgorithms=+ssh-dss,ssh-rsa is no longer needed, but that was bug #351725. This one is about option PubkeyAcceptedKeyTypes=+ssh-rsa, and that's still required, otherwise the server won't accept RSA key generated by the Plasma app: debug1: Will attempt key: /home/8an/.config/kdeconnect/privateKey.pem explicit debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: password,keyboard-interactive,publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/8an/.config/kdeconnect/privateKey.pem sign_and_send_pubkey: no mutual signature supported It happens because the server still doesn't support RSA authentication with SHA-256, only SHA-1: debug2: peer server KEXINIT proposal debug2: KEX algorithms: ecdh-sha2-nistp384,diffie-hellman-group14-sha1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 --- Comment #37 from Lukáš Turek <8...@8an.cz> --- Is there a commit that's supposed to fix it, which I could test in isolation? Because the bug seems fairly random, it appeared in 5.97, disappeared in 5.98, returned in 5.99, seems to be fixed in 5.101... For me it happens only on desktop, never on laptop, even though all the software is exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 --- Comment #34 from Lukáš Turek <8...@8an.cz> --- Created attachment 154828 --> https://bugs.kde.org/attachment.cgi?id=154828=edit Check that URL in fetched data matches originating feed Akregator became unusable for me because of this bug, so I had to find this workaround. When feed RSS is downloaded, feed link in it is checked with the one that was stored in OPML. If these don't match, the update is ignored, it will hopefully work next time. If feed author ever changes its link in RSS, it will stop updating, but that's quite unlikely. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 447552] Changes to medium font size are not kept once Configure dialog is closed
https://bugs.kde.org/show_bug.cgi?id=447552 Lukáš Turek <8...@8an.cz> changed: What|Removed |Added CC||8...@8an.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Lukáš Turek <8...@8an.cz> changed: What|Removed |Added CC||8...@8an.cz -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155
Lukáš Turek <8...@8an.cz> changed:
What|Removed |Added
CC||8...@8an.cz
--- Comment #21 from Lukáš Turek <8...@8an.cz> ---
(In reply to pixelplanetdev from comment #20)
> Got this issue with a new Android 12 phone now.
>
> What is the current workaround?
> HostKeyAlgorthms and PubkeyAcceptedAlgorithms +ssh-rsa
> in .ssh/config did not help.
That's because kdeconnect explicitly disables the use of .ssh/config, I had to
remove this line in plugins/sftp/mounter.cpp to make it work:
<< QStringLiteral("-F") << QStringLiteral("/dev/null") //Do not use
~/.ssh/config
--
You are receiving this mail because:
You are watching all bug changes.
[konqueror] [Bug 307824] Wrong character spacing makes text unreadable
https://bugs.kde.org/show_bug.cgi?id=307824 --- Comment #29 from Lukáš Turek <8...@8an.cz> --- It's also no longer relevant for Akregator, it switched to QtWebEngine long ago. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427091] Kmail gpg bad signature if From header contains non-ascii characters
https://bugs.kde.org/show_bug.cgi?id=427091 --- Comment #4 from Lukáš Turek <8...@8an.cz> --- Created attachment 133939 --> https://bugs.kde.org/attachment.cgi?id=133939=edit Disable protected headers in messagelib I found a workaround: when protected headers are disabled in messagelib, To: and From: headers don't affect the signature, so it validates OK. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427091] Kmail gpg bad signature if From header contains non-ascii characters
https://bugs.kde.org/show_bug.cgi?id=427091 Lukáš Turek <8...@8an.cz> changed: What|Removed |Added CC||8...@8an.cz --- Comment #2 from Lukáš Turek <8...@8an.cz> --- I can confirm the bug, it's a regression after update from 20.04.3 to 20.08.3. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397752] HTML articles appear very small
https://bugs.kde.org/show_bug.cgi?id=397752 --- Comment #7 from Lukáš Turek <8...@8an.cz> --- I have a 1920x1200 display with DPI set to 110, which is still much more than 72 DPI where pixels and points match. I set Medium font size in Akregator to 16, which is the desired value in pixels, roughly matching 10pt set in KDE. QWebEngineSettings::setFontSize also expects the font size in pixels, so the conversion should be either in both places, or none. I chose the latter option, because the font sizes in Akregator then match values in Falkon. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397752] HTML articles appear very small
https://bugs.kde.org/show_bug.cgi?id=397752 --- Comment #4 from Lukáš Turek <8...@8an.cz> --- I didn't test 20.08.3 yet, but the attached patch fixes the problem for me in 20.04.3 and it would apply to current GIT. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397752] HTML articles appear very small
https://bugs.kde.org/show_bug.cgi?id=397752 --- Comment #3 from Lukáš Turek <8...@8an.cz> --- Created attachment 133639 --> https://bugs.kde.org/attachment.cgi?id=133639=edit Remove pointsToPixel conversion -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400937] After deletion, the message remains at the bottom.
https://bugs.kde.org/show_bug.cgi?id=400937 --- Comment #2 from Lukáš Turek <8...@8an.cz> --- Created attachment 117032 --> https://bugs.kde.org/attachment.cgi?id=117032=edit Fix message view scrolling to top on message change -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400937] After deletion, the message remains at the bottom.
https://bugs.kde.org/show_bug.cgi?id=400937 Lukáš Turek <8...@8an.cz> changed: What|Removed |Added CC||8...@8an.cz --- Comment #1 from Lukáš Turek <8...@8an.cz> --- I had a similar problem: deleting messages was OK, but when I opened a folder with an unread message, which is then automatically loaded, the message view wouldn't scroll up. I fixed it by scrolling the view before the new message is loaded - see the attached patch. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397752] HTML articles appear very small
https://bugs.kde.org/show_bug.cgi?id=397752 Lukáš Turek <8...@8an.cz> changed: What|Removed |Added CC||8...@8an.cz --- Comment #1 from Lukáš Turek <8...@8an.cz> --- I have the same problem, but only on some feeds (websites): those that don't set fixed font size (in pt or px), but use relative units (em or rem). I think it happens because QWebEngineSettings::DefaultFontSize expects the size in pixels, not points. However, GrantleeViewFormatter converts the configured Medium Font Size from points to pixels. This inconsistency means that depending on what Medium Font Size you set, you will either have normal fonts on websites and huge fonts in feeds, or tiny fonts on websites and normal fonts in feeds. The simplest fix would be to drop the conversion in GrantleeViewFormatter, but that would change font size in feeds for current users. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388440] scrolling in KMail: "page down" only works once
https://bugs.kde.org/show_bug.cgi?id=388440 Lukáš Turek <8...@8an.cz> changed: What|Removed |Added CC||8...@8an.cz --- Comment #12 from Lukáš Turek <8...@8an.cz> --- I hit this bug in Gentoo after updating to Qt 5.11.1 and it disappeared when I rebuilt messagelib. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 375540] Ambiguous shortcuts crash at startup
https://bugs.kde.org/show_bug.cgi?id=375540 Lukáš Turek <8...@8an.cz> changed: What|Removed |Added CC||8...@8an.cz --- Comment #12 from Lukáš Turek <8...@8an.cz> --- The patch fixed the crash for me when applied to version 16.12.3. I had the shortcut Ctrl+Shift+N assigned to New Tab. -- You are receiving this mail because: You are watching all bug changes.
