Oh and also, people shouldn’t need to press the »Finish« button. If the connection is ok, just connect.
On a related note: Sync does not seem to work for me, my local ownCloud folder is empty although there is stuff in my ownCloud server. It says »remote path: clientsync« – I don’t know exactly what that means, but I assume it would create a folder called »clientsync« in my ownCloud server and then sync just that. But there is no »clientsync« folder either. Sometimes the client also exits, for instance this time I clicked on »Configure« in the context menu. I got a »Segmentation fault« in the console. Let me know how I can help with debugging. On Tue, Jun 26, 2012 at 3:35 PM, Jan-Christoph Borchardt <[email protected]> wrote: > Hey Klaas, nice work! > > > On starting up, I get a popup: > »No server connection has been configured for this ownCloud client. > Please right click on the ownCloud system tray icon and select > Configure to connect this client to an ownCloud server.« > > Instead, the »Configure« popup should just be shown. > > In fact, the right-click menu should only have 2 options when not > connected: »Connect to your ownCloud« and »Quit«. Clicking on the icon > should also bring up the connect to your ownCloud dialog, as it > already does now. > > > (And a note about the secure connection: That should be default and > not needed to be specified via starting the address via https://. It > does not seem to work at all if I just type in »owncube.com« – which > should be possible, and in which case the protocol should be > auto-appended.) > (Also, instead of saying »URL« the wording should be either »link« or > »web address« – I’m not sure about which is the better alternative, > but both are better than »URL« for sure, which is not used or rarely > understood by normal people.) > > > Let me know what you think. I have some more feedback but that’s the > biggest stuff for now. > > (Are the mockups still guiding by the way? > https://gitorious.org/owncloud/mockups/blobs/master/client%20setup.jpg > – let me know if I should improve on them or if something is wrong > with them.) > > > Cheers! > > > On Tue, Jun 26, 2012 at 6:50 AM, Klaas Freitag <[email protected]> wrote: >> On 26.06.2012 15:46, Denis Kot wrote: >>> >>> Bug with increasing /dev/urandom still present >>> http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-920 >>> >>> denis@ws101:~$ lsof -p 4952 | grep urandom | wc -l >>> 39 >>> denis@ws101:~$ lsof -p 4952 | grep urandom | wc -l >>> 43 >> >> I am sorry for that, but I still think that is not ownClouds fault. >> Do you by chance can bring that up in a Ubuntu forum? My gut feeling says >> its related to the SSL stack, but of course not sure. >> >> thanks, >> >> Klaas >> >> >>> >>> 2012/6/26 Klaas Freitag<[email protected]>: >>>> >>>> On 26.06.2012 15:03, Denis Kot wrote: >>>>> >>>>> >>>>> Yes, thanks! Now it works. >>>>> Was unable to autoupdate client via apt and had to update it manually. >>>> >>>> >>>> Thanks for letting me know, I am currently fixing the package. That was a >>>> packaging bug. >>>> >>>> Regards, >>>> >>>> Klaas >>>> >> >> _______________________________________________ >> Owncloud mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
