home.social

#akonadi — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #akonadi, aggregated by home.social.

fetched live
  1. Wenn ihr den Downgrade gemacht habt, oder das Upgrade bisher vermieden habt, empfehle ich die MariaDB-Pakete zu sperren bis bugzilla.suse.com/show_bug.cgi behoben ist. Das geht mit folgendem Befehl:

    sudo zypper addlock --comment 'Pretect against bugzilla.suse.com/show_bug.cgi' 'mariadb*' 'libmariadb*'

    Sobald es ein korrigiertes Update gibt könnt ihr die Sperre dann mit folgendem Befehl wieder aufheben:

    sudo zypper removelock 'mariadb*' 'libmariadb*'

    #openSUSE #MariaDB #Akonadi #Zypper

  2. Why the hell do I constantly have problems with KDE Plasma and that piece of crap Akonadi???? Constant error messages, crashes, etc. whenever I try to connect to a calendar! It doesn't matter at all whether I try the Nextcloud Calendar, iCloud Calendar, or Google Calendar. And when I remove an online calendar, everything freezes—the entire KDE desktop. I’ve had this problem for years, no matter which version of KDE I use. I never have these kinds of problems with GNOME or GNOME Calendar. Akonadi is just a piece of software crap. 💩

    #linux #opensource #freesoftware #kde #akonadi

  3. I am a long-term #KDEPIM user and recently read that due to progress in #SQLite’s performance #Akonadi is now defaulting to that DB on a fresh install.

    A few days ago I took the chance and ran `akonadi-db-migrator --newengine sqlite` and it was both painless and I definitely see both lower resource consumption and the PIM suite seems much snappier too!

    #KDE #Plasma #Kontact #KMail #KOrganizer #Zanshin

  4. Either I am going crazy, or akonadi_imap_resource on Debian 13 requires NetworkManager to be running, and if it is not running it crashes with "invalid nullptr parameter".

    Because you know, that kind of hard dependency would make perfect sense, right?

    :blobcatfacepalm:

    #KDE #Kmail #Akonadi #Debian

  5. ProcessControl: Application "/usr/bin/akonadi_maildispatcher_agent" stopped unexpectedly ( "Process crashed" )

    rocessControl: Application "/usr/bin/akonadi_sendlater_agent" stopped unexpectedly ( "Process crashed"

    Application '/usr/bin/akonadi_imap_resource' crashed too often. Giving up!

    A decade and a half after the first release, #Akonadi remains unusable.

  6. Got pissed off by KMail today, because it stopped sending mails - they just sit there in an outgoing queue and the only way to send them is to restart everything of Akonadi (I already hate Akonadi and I want it to burn to the ground, but this...).

    So, starting to evaluate meli to replace all that crap. It's kinda rough, but it works.

    Not sure that I'm ready to go mutt/neomutt right away, but we shall see.

    #Linux #Email #KDE #Akonadi #Meli

  7. Is there any way to get #akonadi to not just suck out loud on memory usage? #KDE

  8. @cmccullough @markpitblado Aaaah... You've reminded me of those days. I've used Elm, Pine, Alpine and Mutt, but at some point I started using KMail.

    Which was fine until quite recently, when its backend, akonadi started to act up, leading to me having to rebuild my setup three times now, from scratch.

    And I need to zoom through hundreds of mails a day, so maybe... I'll try aerc, too!

    #kmail #kde #akonadi

  9. @daveburb with an exception of a few years (~09-12 on Thunderbird) I've been using KMail since its inception exclusively, since none of the alternatives could come close to it.

    Sure, I had some fights with its underlying #Akonadi, but what KMail offers in functionality, customizability integration and ergonomics easily made up for it.

    @rl_dane

  10. @ticho

    I'm really sorry to hear this. I can tell that it serves me well, but this doesn't help you. You will certainly find a good alternative. Any plans already?

  11. Moin, @Heiko R. das mit KMail hat mich auch überrascht, genauso wie #FairEmail.

    Ich selbst benutze privat hauptsächlich Mutt und zusätzlich auch ein wenig KMail. Ich finde auch, das es in der Vergangenheit im Zusammenhang mit dem #Akonadi -Backend geholpert hatte. Das ist aber merklich weniger geworden.
  12. Today was my last day on , so here are some personal highlights regarding

    ▶️ resources in are now closer to reality
    ▶️ Akonadi Resource for Outlook/Microsoft365 is being worked on (in Rust :rust_ferris: !!)
    ▶️ We have a dedicated EWS server for testing, expect bugfixes!

    It was amazing being on Akademy again after 5 years and seeing all my KDE friends. Thanks everyone for a great Akademy and see you next year :ablobcatheartsqueeze:

  13. A lazy (and free!) Saturday, time to play around and experiment. How about managed by ?

    (Don't worry, I'm not merging this (for now 😈). I'm not even sure if it's a good or a bad idea. And even if it gets merged, it will be optional. I rewrote the process management code to make it extensible, so in the future we can also run Akonadi as a Windows Service or whatever is native on MacOS, with fallback to the mechanism we use today)

  14. @db_geek was definitely related. I stopped it with `akonadictl stop`, then launched , and now it *seems* OK. Font rendering is super weird in KMail, though.

  15. When built and decided in favour of /QML as basis for its GUI stack they also kept their based on , which is no surprise given the fact the alternative would have been and a whole mySQL server running on a mobile.

    So the marriage of Qt and /#libfolks (Evolution data server) looks like this: gitlab.com/ubports/development

  16. @tangeek c'est le but de %CURSOR.

    C'est le positionnement du curseur par défaut quand tu réponds 👌

    Kmail ftw #kde #akonadi #linux #spaghettis