@gpatel-fr
oh funny!.
But seems buggy, it shows the contact profile even in edit mode on click, instead of filling the number

Could anyone that has that kind of issue remember the steps done ?

e.g from 20.04 stable to 24.04.x daily, then back to 24.04.1 stable, then....
If there were remote calendars, etc...

@dR0W said in Calendar and Alarms issue:

@lduboeuf I've removed the mentioned lines and executed the script again and got the same error. The three lines deleted, are restored once script finished.

I've restarted the phone after deleting evolution sources folder, and I have to say you that now both apps work as expected.

I didn't manipulate evolution data server before.

THANKS A LOT for your help!!!!!

i don't like that work around, but if it is fine for you, glad it works
Now we need to know what has happened

Also, i wonder where does that lower case entries come from, i've checked even a Xenial device, and there are not in lower case too. Did you manipulate evolution data server before ?

Well it seems there also others entries that are duplicated:

The easiest way to fix it if you don't care about cleaning all alarms and calendars is to remove the
/home/phablet/.config/evolution/sources folder then restart,

@dR0W said in Calendar and Alarms issue:

[Data Source]
displayname=Personal
displayname[ar]=شخصي
displayname[as]=ব্যক্তিগত
displayname[ast]=Personal
displayname[be]=Асабістыя
displayname[bg]=Лични
displayname[bn]=ব্যক্তিগত
displayname[bn_in]=ব্যক্তিগত
displayname[bs]=Lično
displayname[ca]=Personal
displayname[ca@valencia]=Personal
displayname[cs]=Osobní
displayname[cy]=Personol
displayname[da]=Personligt
displayname[de]=Persönlich
displayname[dz]=རང་དོན།
displayname[el]=Προσωπικά
displayname[en@shaw]=𐑐𐑻𐑕𐑩𐑯𐑩𐑤
displayname[en_ca]=Personal
displayname[en_gb]=Personal
displayname[eo]=Persone
displayname[es]=Personal
displayname[et]=Isiklik
displayname[eu]=Pertsonala
displayname[fa]=شخصی
displayname[fi]=Henkilökohtainen
displayname[fr]=Personnel
displayname[ga]=Pearsanta
displayname[gl]=Persoal
displayname[gu]=ખાનગી
displayname[he]=אישי
displayname[hi]=व्यक्तिगत
displayname[hr]=Osobno
displayname[hu]=Személyes
displayname[id]=Pribadi
displayname[is]=Einka
displayname[it]=Personale
displayname[ja]=個人
displayname[kk]=Жеке
displayname[km]=ផ្ទាល់​ខ្លួន
displayname[kn]=ವೈಯಕ್ತಿಕ
displayname[ko]=개인
displayname[lt]=Asmeniniai
displayname[lv]=Personisks
displayname[mai]=व्यक्तिगत
displayname[mk]=Лично
displayname[ml]=വ്യക്തിപരം
displayname[mr]=खाजगी
displayname[nb]=Personlig
displayname[ne]=व्यक्तिगत
displayname[nl]=Persoonlijk
displayname[nn]=Personleg
displayname[oc]=Personal
displayname[or]=ବ୍ଯକ୍ତିଗତ
displayname[pa]=ਨਿੱਜੀ
displayname[pl]=Osobiste
displayname[pt]=Pessoal
displayname[pt_br]=Pessoal
displayname[ro]=Personal
displayname[ru]=Личное
displayname[rw]=Bwite
displayname[sk]=Osobné
displayname[sl]=Osebno
displayname[sq]=Personale
displayname[sr]=Лично
displayname[sr@latin]=Lično
displayname[sv]=Personligt
displayname[ta]=தனிப்பட்ட
displayname[te]=వ్యక్తిగత
displayname[tg]=Шахсӣ
displayname[th]=ส่วนบุคคล
displayname[tr]=Kişisel
displayname[ug]=شەخسىي
displayname[uk]=Особисте
displayname[vi]=Cá nhân
displayname[xh]=Ezakho Buqu
displayname[zh_cn]=个人
displayname[zh_hk]=個人
displayname[zh_tw]=個人
enabled=true
parent=local-stub
DisplayName=Sin nombre
Enabled=true
Parent=

[Calendar]
backendname=local
color=#77216f
selected=true

[Ubuntu]
accountid=0
applicationid=
autoremove=true
writable=true
metadata=
AccountId=0
ApplicationId=
AutoRemove=true
Writable=true
Metadata=

[Lomiri]
accountid=0
applicationid=
autoremove=true
writable=true
metadata=
AccountId=0
ApplicationId=
AutoRemove=true
Writable=true
Metadata=

ok, just remove this 3 lines in the [Data Source] section:

DisplayName=Sin nombre
Enabled=true
Parent=

and try to run again the script, if it fails again, see which file fails.
Try then to open calendar-app/clock-app ( not sure but maybe a reboot is needed)

@dR0W said in Calendar and Alarms issue:

@lduboeuf Yes, I did it.

could you show the output of
cat /home/phablet/.config/evolution/sources/system-calendar.source

@dR0W said in Calendar and Alarms issue:

@lduboeuf This is what I get:

phablet@ubuntu-phablet:~$ /usr/share/session-migration/scripts/eds-lomiri-ext-migration.py
Migrating EDS sources using Ubuntu extension to Lomiri extension
be8033a4c49ef662e4ecf98a72a5f0d2146fcdc0.source: already has 'Lomiri' section, don't migrate.
Traceback (most recent call last):
  File "/usr/share/session-migration/scripts/eds-lomiri-ext-migration.py", line 50, in <module>
    main()
  File "/usr/share/session-migration/scripts/eds-lomiri-ext-migration.py", line 40, in main
    if migrate_single_source(source_path):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/session-migration/scripts/eds-lomiri-ext-migration.py", line 10, in migrate_single_source
    source.read(source_path)
  File "/usr/lib/python3.12/configparser.py", line 684, in read
    self._read(fp, filename)
  File "/usr/lib/python3.12/configparser.py", line 1075, in _read
    raise DuplicateOptionError(sectname, optname,
configparser.DuplicateOptionError: While reading from PosixPath('/home/phablet/.config/evolution/sources/system-calendar.source') [line 83]: option 'displayname' in section 'Data Source' already exists
phablet@ubuntu-phablet:~$

interesting, some configs are corrupted. Did you have once installed a 24.04.2.x version then back to 24.04.1 or 20.04 before ?

@dR0W said in Calendar and Alarms issue:

@lduboeuf This is the log for Calendar and Clock apps:

Calendar log: https://dpaste.com/54LDR8SMF
Clock log: https://dpaste.com/5MRHK6WB2

Apparently, the problem is the same as yesterday

hmm, i don't see why it failed.
could you manually run and share to us the output:
/usr/share/session-migration/scripts/eds-lomiri-ext-migration.py

@dR0W said in Calendar and Alarms issue:

@lduboeuf said in Calendar and Alarms issue:

grep "eds" /home/phablet/.local/share/session_migration-ubuntu-touch

This what I get now:

phablet@ubuntu-phablet:~$ grep "eds" /home/phablet/.local/share/session_migration-ubuntu-touch
migrated=lomiri-system-settings-datahome-migration.sh;lomiri-gsettings-schema-name-change.sh;lal-cache-migration.sh;lomiri-schemas-gsettings.sh;lomiri-thumbnailer-gsettings-schema-name-change.sh;lomiri-keyboard-gsettings-schema-name-change.sh;luitk-config-migration.sh;eds-lomiri-ext-migration.py;ubuntu-system-settings-keyboard-accountsservice-to-gsettings.py;lomiri-accountsservice-schema-name-change.py;lomiri-system-settings-greeter-data-rename.sh;lomiri-schemas-accountsservice.py;dark-theme-migration.sh;lomiri-schemas-launcher-system-app-rename.py;lomiri-wizard-has-run-migration.sh;03_run-account-polld-hook;lomiri-telephony-service-greeter-data-migration.sh;ldm-db-migration.sh;ubuntu-system-settings-sound-gsettings-to-accountsservice.py;lomiri-system-settings-gsettings-schema-name-change.sh;messaging-app-name-change.sh;lomiri-cache-migration.sh;content-hub-gsettings-schema-name-change.sh;dialer-app-name-change.sh;morph-browser-name-change.sh;03_migrate_signon;lomiri-push-service-rename-migration.sh;lomiri-push-service-migrate-settings.py;libusermetrics-rename-gsettings.sh;address-book-app-name-change.sh;lomiri-thumbnailer-cache-migration.sh;
phablet@ubuntu-phablet:~$

Ok so the migration has run. What is your logs now on calendar and clock app ?

@Ernst-Jan15
Maybe a reinstall with 24.04.1 stable via the installer

@dR0W could you try :
grep "eds" /home/phablet/.local/share/session_migration-ubuntu-touch

if it finds something then the migration has run. But something else needs to be done.
Could you just reboot just in case ?

@dR0W
Also it appears that some device have not received the daily image yet. But please check if the package mentionned before is here

@dR0W said in Calendar and Alarms issue:

@lduboeuf I've switched to daily but that haven't solved the problem.

What does the above commands say ?

Also are you still experiencing the calendar app infinite loading and foe alarms tab in clock app ?

@dR0W said in Calendar and Alarms issue:

@lduboeuf Here is the output to these commands:

phablet@ubuntu-phablet:~$ dpkg -l evolution-data-server-lomiri
dpkg-query: no packages found matching evolution-data-server-lomiri
phablet@ubuntu-phablet:~$ journalctl | grep -5 "Migrating EDS sources"
phablet@ubuntu-phablet:~$ 

oh bad luck, the fix has been merged too late:
https://gitlab.com/ubports/development/core/seeds/ubuntu-touch/-/commits/ubports/24.04-1.x?ref_type=heads

So would be interesting to go to daily ( which is mostly the same than the stable today ) or wait for next stable...

@dR0W said in Calendar and Alarms issue:

@lduboeuf Logs are when I'm in 24.04-1.1.
Relative to custom modifications... I did tried to install Lomiri Plus Essential with Ambot installer to configure round corners when I'm in 24.04 daily but it fails. I don't know if this could be relationed or not.
Thanks for your time.

I don't know if it can interact with the calendar/alarm system.
To make sure can you confirm,

dpkg -l evolution-data-server-lomiri return something

Also in your logs, do you find any "Migrating EDS sources' ( journalctl | grep -5 "Migrating EDS sources" )
and see if you see errors around

@dR0W Now that you are on 24.04-1.1 could you show logs again, ah but maybe you were already in the first post ?

btw the former issues specific to calendar/clock is here:

[26/11/25 15:14] Error opening accounts DB: unable to open database file
[26/11/25 15:14] ag_manager_load_account: assertion 'AG_IS_MANAGER (manager)' failed
[26/11/25 15:14] g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[26/11/25 15:14] Fail to connect with client No se pudo conectar a «Sin nombre:» No se pueden encontrar el «backend» de fábrica para la fuente «system-calendar» ni la extensión «Calendar».
[26/11/25 15:14] g_object_ref: assertion 'G_IS_OBJECT (object)' failed
[26/11/25 15:14] e_cal_client_get_view: assertion 'E_IS_CAL_CLIENT (client)' failed

the /run/user/32011/dconf/user warnings are just the consequence of a confined apps, and is normal if i'm not wrong

Also, did you do anything custom on your device ?

@dR0W
Did you received the last stable release already ? Because this version should fix the issue

said in bugs on UT agenda:

@DJac said in bugs on UT agenda:

for exemple :

• i create a event (all day) from 10 decembre to 15 decembre. Result : OK
• i deplace the event to 20 decembre. it seems te be from 20 to 25 december.
• but after validation, it jump from 19 to 24 december.
• and when i want to change it, the probleme persist.

Ok, got it, i have a pending fix for that, but it needs more work since it has side effects...

Forgot to say that the current "devel" version already fix that iirc: it can be safely installed:
download this file and open it with openstore :
https://gitlab.com/ubports/development/apps/lomiri-calendar-app/-/jobs/12156465069/artifacts/raw/build/aarch64-linux-gnu/app/calendar.ubports_1.1.4-66-g608821d6_arm64.click

Congrats for this initiative. Here is the list of things that come to my mind:

Considered as a blocker for me:

• Battery drains on LTE ( luckily i can still use 2G here and battery-saver app), otherwise having a phone that last less than a full day is not reliable.

"Basic" needs that still missing:

• AGPS
• Data backup and syncing

Annoying, but can be worked around:

• Random OSK crash
• Cellular network re-connection ( reboot is sometimes needed )
• Some users reports Camera freeze ( reboot needed)
• Not possible to select a default target with url-dispatcher or content hub.
• Calendar sync issues ( when it is working it works but when not, it can be painfull to make it works reliabily again )
• MMS does not work if Wifi is On

Polishing:

• back button size or position
• connect to public wifi or via qrcode
• bluetooth robustness and with carkit
• integrated app cleaning and settings for runing without suspension

Otherwise, so proud of UT :).