personal calendar for newly created users has no calendar color set

[mbiebl]

Nextcloud: 13.0.6

When creating a new user, it by default gets a personal addressbook and calendar. Unfortunately, the calendar has not color set by default. Looking at the db dump, I see

INSERT INTO `sgnDV_calendars` (`id`, `principaluri`, `displayname`, `uri`, `synctoken`, `description`, `calendarorder`, `calendarcolor`, `timezone`, `components`, `transparent`) VALUES

(5, 'principals/users/test', 'Personal', 'personal', 1, NULL, 0, NULL, NULL, 'VEVENT,VTODO', 0);

Notice how calendarcolor is set to NULL.
Please pick a reasonable default instead of NULL

[nextcloud-bot]

GitMate.io thinks possibly related issues are #2597 (Calendar Import: "Create Calendar" option fails.), #3014 (Calendar event invitation automatically creates a new 'personal' calendar), #5040 (Upon invitations, calendar "personal" is created although there is a valid calender), #2568 (user can't change language in personal settings), and #1011 (Error while re-creating a user).

[MorrisJobke]

cc @georgehrke

[szaimen]

I'm closing this issue due to inactivity. If this is still happening please make sure to upgrade to the latest version. After that, feel free to reopen.

[mbiebl]

Unfortunately, I can't reopen it seems. Please do so. Afaics his has not been fixed yet.

[szaimen]

So you can reproduce this on NC21.0.2?

[mbiebl]

It seems I still have user calendars where calendarcolor is set to NULL

[mbiebl]

Just create a new use, log in as that user, notice how the "Personal" calendar for that user is set to NULL.
If you think this was fixed, a reference to a commit would be appreciated (or asking before closing bug reports. Simply closing them I find not particularly friendly, tbh).

[szaimen]

I'll try to reproduce this in a monent

[szaimen]

I am actually not able to reproduce this: this user is fresh and the personal calendar has a valid color:

Or what do you mean with calendarcolor is set to NULL?

[szaimen]

or asking before closing bug reports. Simply closing them I find not particularly friendly, tbh

That's why I've asked to reopen the issue if it should still be valid.
But now that I've tried to reproduce this and failed, I think it was correct to close it.