[horde] in horde_histories history_who = 'f'

[Jens-U. Mozdzen]

Hi Steffen,

Zitat von Steffen <skhorde at smail.inf.fh-bonn-rhein-sieg.de>:
> if an user adds/deletes/... events via CalDAV or ActiveSync or  
> Mnemos or Tasks via "Task & notes" for Android, horde_histories gets  
> an entry where history_who is 'f'. I do not have no user 'f' and the  
> users in question do not configured this user 'f', but their own.
>
> I've created a backtrace for one issue, when prefs_init() called  
> user data for the non-existing user 'f'. Here _buildNote() called  
> getUserName(), which queried horde_histories, which returned 'f'.  
> The note is located in my notepad and I've setup the app to use my  
> account.
>
> If I add a new note with "Task& notes" for Android, I get a new  
> entry in horde_histories with history_who = 'f'. The same applies,  
> if I add a new event with CalDAV clients in KDE and Android.
>
> Shouldn't history_who contain the username used to make the changes?  
> Besides the fact, that there might exist the user "f".
> Or might there a configuration mistake?

I just checked our according table - while most of the entries do have  
the user's email address in the history_who field, some do have "0".  
These entries seem to be spread access all applications - object_uid  
does start with "imp:", "turba:", "nag:", "kronolith:" and so on.  
"history_action" is "add, "modify", "delete" - so again spread.

The first occurrence of such an extraordinary entry was at time stamp  
"1357325373" (Jan 4, 2013), mod_seq 382 - almost one year after the  
first history entry (Feb 2012) on this installation. The latest  
occurrence is from yesterday, so it happens with current code, too.

Regards,
Jens