On Tue, May 03, 2016 at 04:20:37PM -0400, Nick wrote:
> The owncloudclient refuses to work and core dumps on non-root user
> Works but throws out warnings on root.. although I feel a little edgy running 
> this client as root.
> 
> Application: owncloudclient
> System: 5.9 Stable
> 
> ###################
> $ owncloud
> (owncloud:30815): GLib-ERROR **: Creating pipes for GWakeup: Too many open 
> files
> Trace/BPT trap (core dumped)
You need to bump openfiles on login.conf, e.g.

  :openfiles-cur=2048:\
  :openfiles-max=4096:\

see login.conf(5), and don't forget to run cap_mkdb when you're done.
You'll also need to log out and back in for it to take effect. When in
doubt check things with ulimit -a and ulimit -Ha


> $ gdb owncloud owncloud.core
> #0 0x0000066932b634c5 in _g_log_abort ()
> from /usr/local/lib/libglib-2.0.so.4200.2
> 
> #####################
> 
> $ su root
> $ owncloud
> 
> (process:12834): GConf-WARNING **: Client failed to connect to the D-BUS 
> daemon:
> 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.
> 
> (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS 
> daemon:
> 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.
> Qt: Session management error: Authentication Rejected, reason : None of the 
> authentication protocols specified are supported and host-based 
> authentication failed
> 
> (owncloud:12834): GConf-WARNING **: Client failed to connect to the D-BUS 
> daemon:
> 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.

This doesn't crash /probably/ because owncloud using root's owncloud
configuration (whatever that is), i.e., it's not monitoring the same
folder as when it is run by you.

> 
> -*-*-*
> 
> Thanks
> 

-- 

Reply via email to