I use a local IMAP server for my mail for many reasons, one of them being the ability to read my mail when I'm offline. Since the last upgrade kmail refuses reading mails for no reason (ip r g ::1 shows a valid route). Preferring "Fake Net" in the solid configuration does not help. The non-alternatives are using a Maildir resource (no support for folder structure) and disconnected mode (why duplicate all the data?). Greetings Timo Debian Release: jessie/sid 900 stable security.debian.org 890 testing http.debian.net 880 unstable http.debian.net 500 wheezy debian.fsmi.uni-karlsruhe.de 500 squeeze debian.fsmi.uni-karlsruhe.de --- Package information. --- Depends (Version) | Installed ===================================================-+-=================== kde-runtime (>> 4:4.10) | 4:4.10.5-1 kdepim-runtime (>= 4:4.10.2) | 4:4.10.5-1 kdepimlibs-kio-plugins | 4:4.10.5-1 libakonadi-contact4 (>= 4:4.10.2) | 4:4.10.5-1 libakonadi-kde4 (>= 4:4.10.2) | 4:4.10.5-1 libakonadi-kmime4 (>= 4:4.10.2) | 4:4.10.5-1 libakonadiprotocolinternals1 (>= 1.5.1) | 1.9.2-2+b1 libc6 (>= 2.14) | libcalendarsupport4 (= 4:4.10.5-2) | libgcc1 (>= 1:4.1.1) | libgpgme++2 (>= 4:4.10.2) | libincidenceeditorsng4 (= 4:4.10.5-2) | libkabc4 (>= 4:4.10.2) | libkcalcore4 (>= 4:4.5.86) | libkcalutils4 (>= 4:4.5.86) | libkcmutils4 (>= 4:4.5.86) | libkdecore5 (>= 4:4.4.95) | libkdepim4 (= 4:4.10.5-2) | libkdeui5 (>= 4:4.10.0) | libkio5 (>= 4:4.5.85) | libkleo4 (= 4:4.10.5-2) | libkmime4 (>= 4:4.10.2) | libknotifyconfig4 (>= 4:4.3.4) | libkontactinterface4 (>= 4:4.10.2) | libkparts4 (>= 4:4.5.85) | libkpgp4 (= 4:4.10.5-2) | libkpimidentities4 (>= 4:4.10.2) | libkpimtextedit4 (>= 4:4.10.2) | libkpimutils4 (>= 4:4.10.2) | libkprintutils4 (>= 4:4.4.95) | libksieveui4 (= 4:4.10.5-2) | libktnef4 (>= 4:4.10.2) | libmailcommon4 (= 4:4.10.5-2) | libmailimporter4 (= 4:4.10.5-2) | libmailtransport4 (>= 4:4.10.2) | libmessagecomposer4 (= 4:4.10.5-2) | libmessagecore4 (= 4:4.10.5-2) | libmessagelist4 (= 4:4.10.5-2) | libmessageviewer4 (= 4:4.10.5-2) | libnepomukcore4 (>= 4:4.9.3) | libpimcommon4 (= 4:4.10.5-2) | libqt4-dbus (>= 4:4.5.3) | libqt4-network (>= 4:4.5.3) | libqt4-xml (>= 4:4.5.3) | libqtcore4 (>= 4:4.7.0~beta1) | libqtgui4 (>= 4:4.8.0) | libqtwebkit4 (>= 2.2.0) | libsolid4 (>= 4:4.3.4) | libsoprano4 (>= 2.1.1) | libstdc++6 (>= 4.1.1) | libtemplateparser4 (= 4:4.10.5-2) | perl | Recommends (Version) | Installed ===========================-+-=========== gnupg2 | 2.0.20-1 gnupg-agent | 2.0.20-1 pinentry-qt4 | 0.8.1-1 OR pinentry-x11 | Suggests (Version) | Installed ==================================-+-============== kaddressbook | 4:4.10.5-2 kleopatra | 4:4.10.5-2 spamassassin | 3.3.2-6 OR bogofilter | OR annoyance-filter | OR spambayes (>= 1.0.4-6) | OR bsfilter | OR crm114 | clamav | 0.97.8+dfsg-1 OR f-prot-installer | procmail | 3.22-20
tags 721608 upstream thanks Hello, the bug you reported is a KDE bug. Please report it via Help -> Report bug... menu item of the respective application or by visiting https://bugs.kde.org/ and following instructions to report a new bug. Debian Qt/KDE maintainers do not have resources to deal with non Debian-specific bugs and therefore it is unlikely that your bug will be solved if you do not report it to KDE developers directly (unless it is/has been reported by somebody else). Whenever you open a bug report on the KDE bug tracking system, or you find that the bug has been already reported on it, you can couple both this Debian bug and the KDE bug together by sending the mail with the text below to control@bugs.debian.org (replace KDE-BUG-URL with the address of the bug report on https://bugs.kde.org/)------------[ copy this ]------------ forwarded 721608 KDE-BUG-URL thanks ------------[ copy this ]------------ Thank you, -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
tags 721608 upstream thanks Hello, the bug you reported is a KDE bug. Please report it via Help -> Report bug... menu item of the respective application or by visiting https://bugs.kde.org/ and following instructions to report a new bug. Debian Qt/KDE maintainers do not have resources to deal with non Debian-specific bugs and therefore it is unlikely that your bug will be solved if you do not report it to KDE developers directly (unless it is/has been reported by somebody else). Whenever you open a bug report on the KDE bug tracking system, or you find that the bug has been already reported on it, you can couple both this Debian bug and the KDE bug together by sending the mail with the text below to control@bugs.debian.org (replace KDE-BUG-URL with the address of the bug report on https://bugs.kde.org/)------------[ copy this ]------------ forwarded 721608 KDE-BUG-URL thanks ------------[ copy this ]------------ Thank you, -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/