Would you explain what statup log you need and how I can get them for you? Can you post the entire startup log not just limited to > Most of the errors are not from Lightning and those that are, are fine (re If not linked to Ligtning directly maybe the problem lie in the User Interface and the calendar widget view (left column and calendar view part.) items not properly populated in the views. 1 above to access my list of Calendar and proper view, then I can switch between Day and Month view. This is the case when no calendar are listed in the left column. I also tried to change the filter to "Currently Selected Day", which adjust accordingly the list in the list item view.Īs for the Calendar view it is set on Week and I cannot switch to Day or Month view. I always set the UI filter to "Events in Current View" because of the performance issue encounter with broader filter (would be nice to have this issue sorted at some point as well but may not be possible while TB is in monolithic architecture :-) > events are known to cause similar issues. > look up reasonable short - unlimited filters like all event or all future > too broad? In general, these filter setting should limit the timespan to > calendar grid, context menu of the task tree in the today pane are not set > Have you made sure that your UI filters (dropddown in the list above the
The reason it is setup this way is because I share my calendar with other users but not my tasks.
Out of 6 calendars only two turned ON one for calendar items and another one used for tasks. I even now disabled the Reminders but still same issue. Network calendars (calDav), provider Fabit using Davical calendar system running on Ubuntu server 16.04. > Can you also describe your calendar setup (which types/providers, offline > _all_ of them and start with only Lightning enabled? > What other addons have you installed? Does this happen also if you disable
describe in previous comment was no longer working for a while until the computer was rebooted and then this workaround worked again!
0 kommentar(er)
