Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating new users not possible #222

Closed
GubblGubbl opened this issue Nov 2, 2012 · 7 comments
Closed

Creating new users not possible #222

GubblGubbl opened this issue Nov 2, 2012 · 7 comments
Labels

Comments

@GubblGubbl
Copy link

Hello,
I'm using a Raspberry Pi (Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux) and the lates owncloud Version 4.5.1 and everytime I create a new user I get this message in the Error Log:

OC_Contacts_Addressbook::OC_Contacts_Addressbook::setActive, id: 1, active: 1

I reinstalled the system using MySQL and SQLite, but both show me the sae error.
And I can not create Shared directories either (but I think that is a result of this error)

@DeepDiver1975
Copy link
Member

@tanghus What should this message on the error log tell us? THX

@tanghus
Copy link
Contributor

tanghus commented Nov 4, 2012

I was positive I had removed that - yes it's gone in stable45, but apparently not in time for 4.5.1. When you create a new user an addressbook gets created. That line is just for debugging, and does nothing in itself.

@GubblGubbl
Copy link
Author

Well, the users are able to login, but the shared folders don't work. The shared folder is displayed to everybody I granted access to, but when clicking on it, the browser redirects to the home folder.

@schiessle
Copy link
Contributor

It is most likely the same bug as described in issue #89. It is already fixed in git master and stable45. Applying the fix posted in the other bug report or disabling the picture app until the next bug fix release should solve the problem.

@tanghus
Copy link
Contributor

tanghus commented Nov 6, 2012

@schiesbn Is it safe to say this is a dupe of issue #89 and close this?

@schiessle
Copy link
Contributor

@tanghus It is (almost) safe. I never could reproduce this bug. During the developer meeting @blizzz and I had access to two systems with this bug, we isolate it and fix it for both systems with the commit mentioned in issue #89. There is also issue #140 where at least one participant mention that this bug could still exists.

But since this is definitely something different than the issue stated at the beginning in this thread I don't mind if you close the bug.

@tanghus
Copy link
Contributor

tanghus commented Nov 6, 2012

@schiesbn Meaning closing this and #89 but not #140 ? #confused ;)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants