Thanks for your advice, however it makes no difference changing login.conf in the way you mentioned.. Still errors out and core dumps. Root can't get access to it now either. Here's my login.conf, I changed the:
:openfiles-cur=2048:\ :openfiles-max=4096:\ on my staff group as well, for which I'm a member of. *-*-*-*-*-*-*-*-*-*-*-*-*-* MY LOGIN.CONF: -*-*-*-*-*-*-*-*-*-*-*-*- # /etc/login.conf default:\ :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/$ :umask=022:\ :datasize-max=2048M:\ :datasize-cur=2048M:\ :maxproc-max=1024:\ :maxproc-cur=512:\ :openfiles-cur=2048:\ :openfiles-max=4096:\ :stacksize-cur=4M:\ :localcipher=blowfish,8:\ :tc=auth-defaults:\ :tc=auth-ftp-defaults: *-*-*-*-*-*-*-*-*-*-*-*-*-* AS REGULAR USER: -*-*-*-*-*-*-*-*-*-*-*-*- $ owncloud (owncloud:29572): GLib-ERROR **: Creating pipes for GWakeup: Too many open files Trace/BPT trap (core dumped) *-*-*-*-*-*-*-*-*-*-*-*-*-* AND AS ROOT: -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- $ su $ owncloud (process:3224): 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:3224): 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:3224): 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:3224): GLib-ERROR **: Creating pipes for GWakeup: Too many open files Trace/BPT trap *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- I can't think what could be causing this issue, not entirely sure how to debug this. -------- Original Message -------- Subject: Re: owncloudclient GUI issues - core dumps when non-root Local Time: May 3, 2016 9:58 PM UTC Time: May 3, 2016 8:58 PM From: zel...@zeloff.org To: CC: misc@openbsd.org 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 > --
