SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64 14.2, SlackwareARM, Debian, CentOS, RHEL, Devuan, Raspbian, Kali
Posts: 15
Rep:
KDE4 Plasma issue when running Nextcloud client
Here's a strange one, I'm running Slackware64 14.2 and I have the Nextcloud client from slackbuilds which uses qt5 also built from slackbuilds. After a few days at random times, KDE will stop responding correctly. For example, I can't switch virtual desktops, I can't click on different programs in my task bar. Alt-tab works as well as several other KDE shortcuts. The only way to fix is to open a new terminal and run 'killall plasma-desktop && plasma-desktop' and after a few seconds my machine is usable again.
I run this in a tmux session so I can keep track of errors and what I've found is there is always this same error when this issue starts.
Code:
void DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
After killing plasma-desktop and starting it again, I get some strange lines, but they might not have anything to do with the error.
Code:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusObjectPath: invalid path ""
plasma-desktop(10920)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
========================> 3 0
static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower.
plasma-desktop(10920)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
file:///usr/lib64/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: TypeError: Result of expression 'listView' [null] is not an object.
file:///usr/lib64/kde4/imports/org/kde/plasma/components/SectionScroller.qml:175: ReferenceError: Can't find variable: sectionsRepeater
file:///usr/lib64/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: Error: Cannot assign [undefined] to QString
file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_62: Possible anchor loop detected on fill.
This has actually been happening for quite some time now, but I'm getting tired of going through this every few days. It has been going so long I don't even remember when it started.
I'm actually seeing similar plasma-desktop lockups on my KDE4 install on 14.2, however, I just chalked mine up to upgrading my graphic's stack in 14.2 to add support for my video card (it was released after 14.2 was, so there's no driver support for it in the stock OS). It's been a minor annoyance, but I haven't seemed to lose anything when restarting plasma-desktop, so I haven't bothered researching it or checking logs.
I don't use Nextcloud, so our issues may not be related or your issue might have nothing to do with Nextcloud. However, I am running transgui, which is a qt5 application, so I supposed it's possibly tied to qt5 usage.
Distribution: Slackware64 14.2, SlackwareARM, Debian, CentOS, RHEL, Devuan, Raspbian, Kali
Posts: 15
Original Poster
Rep:
I'm pretty sure it has to do with Nextcloud because if I don't run the application I seem to never have the issue. Maybe I should not run it for a longer period of time to see if the problem pops back up. It could also be that I have several other qt5 applications always running, I wonder if that could be the cause.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.