The problem seems to be here line 381
https://github.com/Alinto/sogo/blob/master/UI/Scheduler/UIxCalListingActions.m
mails = [[theRecord objectForKey: @"c_partmails"] componentsSeparatedByString:
@"\n"];
My guess is the value for c_partmails is not a NSString as expected. You cand
add a breakpoint there and cheking the value of theRecord:
break UI/Scheduler/UIxCalListingActions.m:381
y
run
Then when stopped :
po theRecord
You could also check in your database the type of column “c_partmails” from
table “sogo_quick_appointment”.
Regards,
Quentin
From: users-requ...@sogo.nu <users-requ...@sogo.nu> On Behalf Of "Raoul
Schroeder"
Sent: dimanche 10 septembre 2023 14:25
To: users@sogo.nu
Subject: AW: [SOGo] Problems with calendar view
Thanks for the gdb instructions.
So, when opening the view, once again it happens in alarmlist:
Sep 10 14:06:27 sogod [191697]: 2a01:c22:d4a8:ec00:6919:24c2:ed24:5281 "GET
/SOGo/so/bbbbbb/Calendar/alarmslist?browserTime=1694347587 HTTP/1.1" 200 204/0
0.007 - - 0 - 12
WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future
version.
Breakpoint 1, -[NSException raise] (self=0x555555f62f40, _cmd=0x7ffff7339fe0
<_OBJC_SELECTOR_TABLE+480>) at ./Source/NSException.m:1595
1595 ./Source/NSException.m: No such file or directory.
(Is the “no such file or directory an issue”? I did follow the symbol install
to the letter)
The bt looks like this:
(gdb) bt
#0 -[NSException raise] (self=0x555555f62f40, _cmd=0x7ffff7339fe0
<_OBJC_SELECTOR_TABLE+480>)
at ./Source/NSException.m:1595
#1 0x00007ffff6ff593a in +[NSException raise:format:arguments:]
(self=<optimized out>, _cmd=<optimized out>,
name=0x7ffff733a990 <_OBJC_INSTANCE_5>, format=<optimized out>,
argList=0x7fffffffb610)
at ./Source/NSException.m:1487
#2 0x00007ffff6ff6639 in +[NSException raise:format:] (self=0x7ffff733a320
<_OBJC_Class_NSException>,
_cmd=<optimized out>, name=0x7ffff733a990 <_OBJC_INSTANCE_5>,
format=0x7ffff73753d0 <_OBJC_INSTANCE_11.19>) at ./Source/NSException.m:1472
#3 0x00007ffff705ca6e in -[NSObject doesNotRecognizeSelector:]
(self=0x555555721a60, _cmd=<optimized out>,
aSelector=<optimized out>) at ./Source/NSObject.m:1740
#4 0x00007ffff712c288 in GSFFIInvocationCallback (cif=0x555555f7cc40,
retp=0x7fffffffb950,
args=<optimized out>, user=<optimized out>) at
./Source/GSFFIInvocation.m:606
#5 0x00007ffff5d4e7ec in ?? () from /lib/x86_64-linux-gnu/libffi.so.8
#6 0x00007ffff5d4f050 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8
#7 0x00007ffff2614765 in -[UIxCalListingActions _fixParticipants:]
(self=0x555555f92c00,
_cmd=0x7ffff2640230 <_OBJC_SELECTOR_TABLE+1200>, theRecord=0x5555560c41d0)
at UIxCalListingActions.m:381
#8 0x00007ffff26161bd in -[UIxCalListingActions
_fetchFields:forComponentOfType:] (self=0x555555f92c00,
_cmd=0x7ffff26403a0 <_OBJC_SELECTOR_TABLE+1568>, fields=0x555555722910,
component=0x7ffff263ede0 <_OBJC_INSTANCE_74.52>) at
UIxCalListingActions.m:621
#9 0x00007ffff2619a22 in -[UIxCalListingActions eventsBlocksAction]
(self=0x555555f92c00,
_cmd=0x555556066870) at UIxCalListingActions.m:1462
#10 0x00007ffff7966f0c in -[WODirectAction performActionNamed:]
(self=0x555555f92c00,
_cmd=0x7ffff27f6f90 <_OBJC_SELECTOR_TABLE+720>, _actionName=0x555555fba690)
at WODirectAction.m:97
#11 0x00007ffff27e1bda in -[SOGoDirectAction performActionNamed:]
(self=0x555555f92c00,
_cmd=0x7ffff7b45cc0 <_OBJC_SELECTOR_TABLE+928>, _actionName=0x5555558d9270)
at SOGoDirectAction.m:271
#12 0x00007ffff7a05f4a in -[SoActionInvocation
callOnObject:withPositionalParametersWhenNotNil:inContext:] (
self=0x5555557261f0, _cmd=0x7ffff7b45cf0 <_OBJC_SELECTOR_TABLE+976>,
_client=0x5555556caac0,
_positionalArgs=0x0, _ctx=0x55555621d850) at SoActionInvocation.m:300
#13 0x00007ffff7a06097 in -[SoActionInvocation callOnObject:inContext:]
(self=0x5555557261f0,
_cmd=0x7ffff7b45c10 <_OBJC_SELECTOR_TABLE+752>, _client=0x5555556caac0,
_ctx=0x55555621d850)
at SoActionInvocation.m:318
#14 0x00007ffff7a05cac in -[SoActionInvocation
callOnObject:withPositionalParametersWhenNotNil:inContext:] (
self=0x5555558f1110, _cmd=0x7ffff7b45cf0 <_OBJC_SELECTOR_TABLE+976>,
_client=0x5555556caac0,
s=0x0, _ctx=0x55555621d850) at SoActionInvocation.m:260
#15 0x00007ffff7a06097 in -[SoActionInvocation callOnObject:inContext:]
(self=0x5555558f1110,
_cmd=0x7ffff7b3f9c0 <_OBJC_SELECTOR_TABLE+672>, _client=0x5555556caac0,
_ctx=0x55555621d850)
at SoActionInvocation.m:318
#16 0x00007ffff79ffc0a in -[SoObjectMethodDispatcher dispatchInContext:]
(self=0x555555f494a0,
_cmd=0x7ffff7b41e60 <_OBJC_SELECTOR_TABLE+1536>, _ctx=0x55555621d850) at
SoObjectMethodDispatcher.m:192
#17 0x00007ffff7a02486 in -[SoObjectRequestHandler
handleRequest:inContext:session:application:] (
self=0x555555aa1e90, _cmd=0x7ffff7acbc30 <_OBJC_SELECTOR_TABLE+848>,
_rq=0x555555a2c070,
_ctx=0x55555621d850, _sn=0x0, app=0x55555596e640) at
SoObjectRequestHandler.m:584
#18 0x00007ffff797ab78 in -[WORequestHandler handleRequest:]
(self=0x555555aa1e90,
_cmd=0x7ffff7a941b0 <_OBJC_SELECTOR_TABLE+1616>, _request=0x555555a2c070)
at WORequestHandler.m:240
#19 0x00007ffff7934304 in -[WOCoreApplication dispatchRequest:usingHandler:]
(self=0x55555596e640,
_cmd=0x7ffff7a94200 <_OBJC_SELECTOR_TABLE+1696>, _request=0x555555a2c070,
handler=0x555555aa1e90)
at WOCoreApplication.m:712
#20 0x00007ffff7934673 in -[WOCoreApplication dispatchRequest:]
(self=0x55555596e640,
_cmd=0x555555567620 <_OBJC_SELECTOR_TABLE+1664>, _request=0x555555a2c070)
at WOCoreApplication.m:752
#21 0x000055555555dafb in -[SOGo dispatchRequest:] (self=0x55555596e640,
_cmd=0x7ffff7b31d20 <_OBJC_SELECTOR_TABLE+1760>, _request=0x555555a2c070)
at SOGo.m:584
#22 0x00007ffff79ee44f in -[WOHttpTransaction _run] (self=0x555555f237a0,
_cmd=0x7ffff7b31d50 <_OBJC_SELECTOR_TABLE+1808>) at WOHttpTransaction.m:566
#23 0x00007ffff79ee821 in -[WOHttpTransaction run] (self=0x555555f237a0,
_cmd=0x7ffff7b2e270 <_OBJC_SELECTOR_TABLE+1168>) at WOHttpTransaction.m:619
#24 0x00007ffff79e9d65 in -[WOHttpAdaptor runConnection:] (self=0x55555586ebd0,
_cmd=0x7ffff7b2e310 <_OBJC_SELECTOR_TABLE+1328>, _socket=0x555555b0d320) at
WOHttpAdaptor.m:373
#25 0x00007ffff79e9fc0 in -[WOHttpAdaptor _handleAcceptedConnection:]
(self=0x55555586ebd0,
_cmd=0x7ffff7b2e320 <_OBJC_SELECTOR_TABLE+1344>,
_connection=0x555555b0d320) at WOHttpAdaptor.m:407
#26 0x00007ffff79ea44d in -[WOHttpAdaptor _handleConnection:]
(self=0x55555586ebd0,
_cmd=0x7ffff7b2e3c0 <_OBJC_SELECTOR_TABLE+1504>, connection=0x555555b0d320)
at WOHttpAdaptor.m:466
#27 0x00007ffff79ea96a in -[WOHttpAdaptor acceptConnection:]
(self=0x55555586ebd0,
_cmd=0x7ffff7b2e230 <_OBJC_SELECTOR_TABLE+1104>,
_notification=0x555555a192d0) at WOHttpAdaptor.m:527
#28 0x00007ffff704da31 in -[NSNotificationCenter _postAndRelease:]
(self=0x555555738f40,
_cmd=<optimized out>, notification=0x555555a192d0) at
./Source/NSNotificationCenter.m:1198
But I do not think the backtrace is usable without the symbols in
NSExceptions.m – at least I presume this is why it says optimized out?
Thanks,
Raoul
Von: users-requ...@sogo.nu <mailto:users-requ...@sogo.nu>
<users-requ...@sogo.nu <mailto:users-requ...@sogo.nu> > Im Auftrag von qhivert
Gesendet: Sonntag, 10. September 2023 13:25
An: users@sogo.nu <mailto:users@sogo.nu>
Betreff: RE: [SOGo] Problems with calendar view
Indeed, nothing wrong with your event.
To debug further you could use gdb to add breakpoint. The process is documented
here -> https://www.sogo.nu/support/faq/how-do-i-debug-sogo.html
Follow the steps to add a breakpoint when any Exception is raised, then get the
backtrace to see where in the code it fails.
Regards,
Quentin
From: users-requ...@sogo.nu <mailto:users-requ...@sogo.nu>
<users-requ...@sogo.nu <mailto:users-requ...@sogo.nu> > On Behalf Of "Raoul
Schroeder"
Sent: dimanche 10 septembre 2023 11:28
To: users@sogo.nu <mailto:users@sogo.nu>
Subject: AW: [SOGo] Problems with calendar view
Thank you very much. I was worried no one was going to reply, so thanks for
taking notice.
It is the latter case, and it does not matter if you create it within
Outlook/Android with ActiveSync, or within SOGo web itself. After you create
one event, the web view no longer works.
I am not sure it is a bug within SOGo, though. Others would have noticed it. I
feel like it is an issue with my installation specifically, but there is not
enough to the error message for me to understand what would be the underlying
issue.
Here is a calendar event export from mysql:
| 4287-64F86880-1-169365E0.ics | BEGIN:VCALENDAR
PRODID:-//Inverse inc./SOGo 5.8.4//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Europe/Berlin
LAST-MODIFIED:20230523T092157Z
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:4287-64F86880-1-169365E0
SUMMARY:Test Neu
LOCATION:Test
CLASS:PUBLIC
X-SOGO-SEND-APPOINTMENT-NOTIFICATIONS:NO
TRANSP:OPAQUE
DTSTART;TZID=Europe/Berlin:20230906T140000
DTEND;TZID=Europe/Berlin:20230906T150000
CREATED:20230906T115528Z
DTSTAMP:20230906T115528Z
LAST-MODIFIED:20230906T115528Z
END:VEVENT
END:VCALENDAR | 1694001328 | 1694001328 | 0 | NULL |
Thanks,
Raoul
Von: users-requ...@sogo.nu <mailto:users-requ...@sogo.nu>
<users-requ...@sogo.nu <mailto:users-requ...@sogo.nu> > Im Auftrag von qhivert
Gesendet: Sonntag, 10. September 2023 09:27
An: users@sogo.nu <mailto:users@sogo.nu>
Betreff: RE: [SOGo] Problems with calendar view
Hello,
Welcome to SOGo 😊
Very strange behavior. Is the problem when you create an event or when an event
has been created and then the calendar view fails?
If it’s the first case, check with your browser debug tool the content of the
request POST “saveAsAppointment”
In the second case, it would be good to see how the event is stored in your
database.
I strongly suggest you open an issue on https://bugs.sogo.nu. If your account
is new, then send an email to b...@sogo.nu <mailto:b...@sogo.nu> with your
username so we can enable it to report.
Quentin
From: users-requ...@sogo.nu <mailto:users-requ...@sogo.nu>
<users-requ...@sogo.nu <mailto:users-requ...@sogo.nu> > On Behalf Of "Raoul
Schroeder"
Sent: jeudi 7 septembre 2023 10:10
To: users@sogo.nu <mailto:users@sogo.nu>
Subject: [SOGo] Problems with calendar view
Hello all,
I am relatively new to SOGo, having used Zarafa/Kopano for over 10 years until
they stopped all development to it.
It took me a while to figure out the differences between the two systems and
getting SOGo to work – especially figuring out how the WOWhelper setting gets
overridden, even though it is stated clearly in the documentation.
Anyway, I got a problem now that I cannot figure out. My calendar views work
perfectly only until there are appointments in it. Then it ends up with request
failed, but even with debug settings on, there is very little in terms of error
messages.
It all comes down to exceptions thrown by malloc:
"GET /SOGo/so/aaaaaaa/Calendar/alarmslist?browserTime=1694071570 HTTP/1.1" 200
60/0 0.007 - - 0 - 13
2023-09-07 09:26:14.268 sogod[26468:26468] EXCEPTION: <NSException:
0x55ebf532ec80> NAME:NSInvalidArgumentException REASON:NSDataMalloc(instance)
does not recognize componentsSeparatedByString: INFO:(null)
Or:
"GET /SOGo/so/bbbbbbb/Calendar/alarmslist?browserTime=1694071657 HTTP/1.1" 200
60/0 0.007 - - 0 - 14
2023-09-07 09:27:40.841 sogod[38833:38833] EXCEPTION: <NSException:
0x55ebf53bb0c0> NAME:NSInvalidArgumentException
REASON:[NSDataMalloc-jsonRepresentation] should be overridden by subclass
INFO:(null)
It seems to be consistently happening with the alarmslist, and it looks like
NSDataMalloc is getting null pointers?
On ActiveSync, I can see the calendar entries on both Outlook 2019 as well as
Android
I am running on the most recent snapshot of 5.8.4 on Ubuntu 22.04 (5.9 is still
masked in the repository)
Thanks,
Raoul
