Nextcloud-client goes <defunct> - how do I debug?

Hello all :slight_smile:

I’m using nextcloud-client as a snap, and just noticed it isn’t working anymore on my desktop machine.

ps aux | grep nextcloud reports the following:

jeffrey  14731  4.8  0.0      0     0 ?        Zl   12:29   0:00 [nextcloud] <defunct>

Starting nextcloud-client from commandline, yields the following output:

jeffrey@mantra:~$ /snap/bin/nextcloud-client
static QPlatformTheme* QKdeTheme::createKdeTheme(): Unable to determine KDE dirs                                                                                                                                                               
QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.229\" (uid=1000 pid=15100 comm=\"nextcloud \") interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=1118 comm=\"/usr/sbin/NetworkManager --no-daemon \")"                   
QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.229\" (uid=1000 pid=15100 comm=\"nextcloud \") interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=1118 comm=\"/usr/sbin/NetworkManager --no-daemon \")"                   
"Object path cannot be empty"  

Would anyone be interested in a strace of the application?

Since I am rather new to snap, I don’t know if the apparmor warnings are the cause of the issue.

Thanks in advance! :slight_smile:

I have resolved the issue by removing the snap, removing the ~/snap/nextcloud-client directory, and installing the snap again.