FIXED: Latest mysql upgrade (5.5.53-0+deb8u1) causes Akonadi to fail to start
Hey, You hopefully all saw the "security update" for akonadi, that fixes the non stating issue: https://www.debian.org/security/2016/dsa-3714 > I am using Akonadi with MariaDB since quite a while. @martin: please keep in mind, that this issue with mysql-server is a problem at Debian stable. As I know you are using unstable (KF5 based kdepim). Promoting to switch to MaraDB should mention, that you havn't tested this switch for stable. <- Or did you test this on stable too? Never the less you are right about promoting the switch- also upstream suggests to switch to MariaDB for current kdepim (KF5 based). > Works marvellously. I just did an mysql_upgrade after a while to upgrade to > fix some warnings in log, but it worked before that as well. Strange - the maintainer for akonadi told me, that MariaDB and MySQL both should detect a new installed version and perform an update automatically. Or are you were talking about, what you did after the switch? Best Regards, Sandro signature.asc Description: This is a digitally signed message part.
Re: plasmashell is broken in sid ;-(
Hi,
I cannot see your problem on 3 machines. What happens if you remove the
plasmoid for the digital clock?
Besides that you should start plasmashell as user: kstart plasmashell
greetz
devil
Am 16.11.2016 17:32 schrieb BogDan:
Hi,
I dist-upgraded my sid today, and it seems plasmashell is broken:
bogdan@zmeu:~$ killall plasmashell bogdan@zmeu:~$ plasmashell
No metadata file in the package, expected it at:
"/usr/share/wallpapers/Fog_on_the_West_Lake/contents/images/"
No metadata file in the package, expected it at:
"/usr/share/wallpapers/Fog_on_the_West_Lake/contents/images/"
No metadata file in the package, expected it at:
"/usr/share/wallpapers/Fog_on_the_West_Lake/contents/images/"
inotify_add_watch("/var/lib/samba/usershares") failed: "Permission
denied"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83:
TypeError: Cannot read property 'Layout' of null
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27:
Unable to assign [undefined] to QStringList
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37:
TypeError: Cannot read property 'DateTime' of undefin
ed
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5:
QML Text: Cannot anchor to a null item.
Then it hangs, after a few minutes (10 to 15) it manages to continue
and it prints the following log:
QXcbClipboard::setMimeData: Cannot set X11 selection owner
QXcbClipboard::setMimeData: Cannot set X11 selection owner
libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
Notifications service registered
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:99:
TypeError: Cannot read property of null
: QML QQuickLayoutAttached: Binding loop detected for
property "minimumWidth"
: QML QQuickLayoutAttached: Binding loop detected for
property "minimumWidth"
Plasma Shell startup completed
: QML QQuickLayoutAttached: Binding loop detected for
property "preferredWidth"
QXcbClipboard::setMimeData: Cannot set X11 selection owner
Registering ":1.78/org/ayatana/NotificationItem/chrome_app_indicator_1"
libkcups: 0
libkcups: 0
Both point size and pixel size set. Using pixel size.
networkmanager-qt: void
NetworkManager::NetworkManagerPrivate::propertiesChanged(const
QVariantMap&) Unhandled property "AllDevices"
networkmanager-qt: void
NetworkManager::NetworkManagerPrivate::propertiesChanged(const
QVariantMap&) Unhandled property "Devices"
networkmanager-qt: void
NetworkManager::NetworkManagerPrivate::propertiesChanged(const
QVariantMap&) Unhandled property "GlobalDnsConfiguration"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "S390Subchannels"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "LldpNeighbors"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "Real"
networkmanager-qt: virtual void
NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unha
KdePIM results testing migration from Plasma 4 to Plasma 5
I decided to set up a VM to test how well my KdePIM data would migrate from Plasma 4 to Plasma 5. I used the KDEPIM settings exporter tool. Results were...mixed. 1. My newsfeeds were fine 2. My messages imported alright...but they were imported as a separate directory structure. Long story short, I now have two "inboxes"-one of which is empty. 2a. weirdly, it knows to send new messages to the inbox that already has my data in it. 2c. It is impossible to get rid of the empty one. 3. My mail filters silently COMPLETELY failed to import 4. My mail transport info imported fine, except that my incoming and outgoing transports lost their human readable names and are replaced with titles like "akonadi-resource-125467a" -- annoying but not a huge issue. 5. Local Contacts imported fine 5a. gmail contacts are nowhere to be found. 6. Calender and tasks silently failed to import, Something tells me this may be a Google Calenders issue. 7. I did not test KAlarms I should note that I have multiple gmail calanders and accounts plus my local resource. I also got nonsensical dialog boxes about providing a directory for my gmail contact and calanders-- which gave me options to put directories into my mailbox(??). How do I go about providing bug reports from here? Thanks, --Shawn
Re: KdePIM results testing migration from Plasma 4 to Plasma 5
Hello. Am Mittwoch, 16. November 2016, 13:31:12 CET schrieb Shawn Sörbom: > 2. My messages imported alright...but they were imported as a separate > directory structure. Long story short, I now have two "inboxes"-one of > which is empty. I didn´t use any KDEPIM Settings Importer or other import functionality in KMail. I just moved the maildir directories over to the new location in ~/.local/share/local-mails and pointed the maildir resource there, then gave it some time to synchronise. Also I let it pick up the old kmailrc. Okay, there is one additional step: Before that with KDEPIM 4 I moved all mbox archival folders I had in the mixed maildir resource to an extra resource and switched the main maildir resource from mixed maildir to plain maildir. I still didn´t point a mixed maildir resource to the old archived mails in KDEPIM 5 as last times I tried to do it ate all memory. Maybe you have two mail related resources now. If so you can remove one with Akonadiconsole for example. But make sure to pick the right one :). But even if you pick to wrong one, you can recreate a maildir resource and point it to the maildir location again, as deleting the resource does not delete the data it handles. Read: Akonadi misconception #1: where is my data? Submitted by amantia https://blogs.kde.org/2011/11/13/akonadi-misconception-1-where-my-data And this one: akonadi/KDE PIM backup/restore https://mail.kde.org/pipermail/kdepim-users/2016-October/000351.html > How do I go about providing bug reports from here? Thats a tough one. Why? - I think upstream as in bugs.kde.org would be the right recipient. - But I think upstream neither has the interest nor the manpower to handle issues related to migrate from KDEPIM 4 to 5 anymore – unless it a fix for a bug reproducable within KDEPIM + Akonadi 5. Stable Debian users are among the latest users to migrate. - Quite some of the issue like loosing filters may already be reported and lingering in upstream bugzilla. - Report in Debian then? I think Debian Qt/KDE maintainers do not have the resources to do much more than to refer to upstream. I am happy they are able to provide packages, although for KDEPIM it would be good to have 16.08 instead of 16.04, but this AFAIK is still blocked by packaging Qt WebEngine, which basically is a port of Chromium´s Blink webengine. Still if you want to report anything: Good luck! Otherwise I suggest to struggle your way through. Review resources in this list and in upstream kdepim-users list. Especially in kdepim-users mailing list, but I think also here I covered migration issues more than once. And so did others. Most if not all questions have been answered already and I don´t even completely recall it all. I migrated more than a year ago and forgot most of the process. If you need help, ask. At least you do the migration only once. I especially would ask in kdepim-users for any open migration issues. There are a lot of users who did the migration and there are upstream developers, too. Am I happy with that? Not really. But thats how I see the situation. Migrating from KDEPIM 4 to 5 has been rough for many users. Thanks, -- Martin
