https://bugs.kde.org/show_bug.cgi?id=473254
--- Comment #3 from m.eik michalke ---
the package may technically not be out-of-date, it is just not compatible with
the R version installed. that is if it still works with the R version shipped
with arch and you upgraded R from a third party repo
https://bugs.kde.org/show_bug.cgi?id=473254
m.eik michalke changed:
What|Removed |Added
CC||bugs.kde.org@ad.geldunterga
https://bugs.kde.org/show_bug.cgi?id=466851
Bug ID: 466851
Summary: support custom highlighting markers
Classification: Applications
Product: kate
Version: 22.04.3
Platform: Other
OS: All
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=381366
m.eik michalke changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=381715
m.eik michalke changed:
What|Removed |Added
Status|CONFIRMED |REPORTED
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=381715
m.eik michalke changed:
What|Removed |Added
Ever confirmed|0 |1
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=343186
--- Comment #6 from m.eik michalke ---
i no longer face this issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375843
m.eik michalke changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=404431
--- Comment #5 from m.eik michalke ---
(In reply to Matthias from comment #4)
> Sorry, my bad. The bug can be triggered with this script:
yes, thanks. i can replicate the issue with this code.
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=404431
m.eik michalke changed:
What|Removed |Added
CC||bugs.kde.org@ad.geldunterga
https://bugs.kde.org/show_bug.cgi?id=459050
Bug ID: 459050
Summary: snippet variable reliably picks middle name instead of
family name
Product: kmail2
Version: 5.20.3
Platform: Ubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=454723
m.eik michalke changed:
What|Removed |Added
CC||bugs.kde.org@ad.geldunterga
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #19 from m.eik michalke ---
(In reply to m.eik michalke from comment #18)
> after that kontact was *instantly* able to fetch contacts and calendars. so
> all i'm missing is a way to tell kontact/akonadi to try IPv4 first.
i've
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #18 from m.eik michalke ---
(In reply to m.eik michalke from comment #17)
> turns out: using a custom port
> an the server behind a NAT router might be the real issue in my case. at
> first 'openssl' kept waiting for a respons
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #17 from m.eik michalke ---
(In reply to Benjamin from comment #15)
> - Update nextcloud to the newest release
> - Install openssl 3 on the server where the nc instance is running
actually, i'm already running nextcloud 24 and the
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #14 from m.eik michalke ---
i checked with "akonadictl --verbose start" and don't see any errors regarding
"qt.network.ssl", it just shows the HTTP error (0) without any further warnings
or errors.
i also configured
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #13 from m.eik michalke ---
glad you solved the problem on your side! however, installing libssl-dev didn't
solve it for me, i'm still getting the "HTTP error (0)" response.
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #8 from m.eik michalke ---
(In reply to gjditchfield from comment #7)
> My second wild guess is that Qt and your browser use different
> configurations;
> Chrome uses a different SSL library, for instance.
that would explain why a
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #5 from m.eik michalke ---
(In reply to gjditchfield from comment #4)
> I use KOrganizer 5.20.0 successfully with two different Nextcloud servers,
> running on KDE Neon (which is basically Ubuntu 20.04). As a wild guess,
>
https://bugs.kde.org/show_bug.cgi?id=453121
m.eik michalke changed:
What|Removed |Added
CC||bugs.kde.org@ad.geldunterga
https://bugs.kde.org/show_bug.cgi?id=408272
m.eik michalke changed:
What|Removed |Added
CC||bugs.kde.org@ad.geldunterga
https://bugs.kde.org/show_bug.cgi?id=428431
Bug ID: 428431
Summary: support the "memory hole" spec to encrypt/decrypt mail
headers
Product: kmail2
Version: 5.13.3
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=353317
m.eik michalke changed:
What|Removed |Added
CC||bugs.kde.org@ad.geldunterga
https://bugs.kde.org/show_bug.cgi?id=423794
--- Comment #2 from m.eik michalke ---
i can confirm the problem is also solved in kmail 5.13.3.
i do agree that 5.7.3 is pretty old. however, users of widely used distros like
kubuntu 18.04 LTS will continue to run KDE plasma 5.12 LTS and older
https://bugs.kde.org/show_bug.cgi?id=423794
Bug ID: 423794
Summary: 'kmail --identity' doesn't set the identity's sent
folder
Product: kmail2
Version: 5.7.3
Platform: Ubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=401198
--- Comment #1 from m.eik michalke ---
my workaround stopped working. i am losing mails on a daily basis!
there are two choices: either i leave the duplicate mails in the folders, in
which case akonadi is stuck and doesn't fetch new mails. or i remove
https://bugs.kde.org/show_bug.cgi?id=403706
m.eik michalke changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
27 matches
Mail list logo
