client
client copied to clipboard
[QA] nemo plugin spams text console
Pre-submission Checks
- [X] I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
- [X] I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.
Describe the QA issue
Seen while testing client 2.11.1 on Linux Mint
- connect client with e.g. demo.owncloud.org
- Install nemo *-nemo browser integration package.
- kill all nemo
- start
nemo &from the command line. Keep that shell open - quit the owncloud client
- nemo starts producing messages on the text console. e.g.
Could not connect to unix socket /run/user/1000/testpilotcloud/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/btr/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/ocfablabnbg/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/testpilotcloud/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/btr/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/ocfablabnbg/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/testpilotcloud/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/btr/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/ocfablabnbg/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/testpilotcloud/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/btr/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/ocfablabnbg/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/testpilotcloud/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/btr/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/ocfablabnbg/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/testpilotcloud/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/btr/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/ocfablabnbg/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/testpilotcloud/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/btr/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/ocfablabnbg/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/testpilotcloud/socket. [Errno 2] No such file or directory
Could not connect to unix socket /run/user/1000/btr/socket. [Errno 2] No such file or directory
- One message per 10 seconds.
- The shell is thus basically unusable.
Expected behaviour:
- only one message immediately, then none, or only hourly reminders.
Steps to reproduce the issue
.
Screenshots
.
Expected behavior
.
Actual behavior
.