Osmo Calendar and Organizer not working properly

[Federico]

Hi everyone,
the other day I bought a flight to visit my parents for Christmas, and I needed a calendar to count the days of my visit, since I also needed to buy parking for my car at the airport and the price is calculated per day. Now: I couldn't find any calendar on the system, and this seemed strange to me, since there was one in the past if I remember well (I don't remember if on Buster or Dunfell).
Anyway, I had to use my phone, that was no problem really, but there is an organizer indeed, isn't it?
Today during boot immediately after the X server started I saw a new window in front of my eyes, which immediately disappeared after a couple of seconds: it was the window of Osmo: Calendar and Organizer. Therefore, I wanted to start it, to maximize its window, to use it somehow. In my system tray there's no icon for Osmo:

Screenshot.png (8.17 KiB) Viewed 519 times

If I click on Menu --> Personal --> Osmo Personal Organizer I get the following:

Screenshot(1).png (42.57 KiB) Viewed 519 times

So I thought that for some reason the icon wasn't working, and I thought that I could kill its process and re-launch it, in order to troubleshoot it somehow.
When I executed:

Code: Select all

# ps aux | grep osmo
root     10224  0.0  0.0   6392  2088 pts/0    S+   11:13   0:00 grep osmo
# kill 10224
bash: kill: (10224) - No such process
# 

I found out that the Osmo process ID is costantly changing:

Code: Select all

# ps aux | grep osmo
root     10531  0.0  0.0   6392  2200 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10535  0.0  0.0   6392  2128 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10538  0.0  0.0   6392  2200 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10541  0.0  0.0   6392  2288 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10545  0.0  0.0   6392  2288 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10560  0.0  0.0   6392  2120 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10563  0.0  0.0   6392  2156 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10567  0.0  0.0   6392  2288 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10570  0.0  0.0   6392  2288 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10588  0.0  0.0   6392  2280 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10592  0.0  0.0   6392  2284 pts/0    S+   11:14   0:00 grep osmo
# 

Now: for sure I don't know, but this probably means that the program is in a loop: it costantly restarts.

If I try to execute:

Code: Select all

# kill `pidof osmo`
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
#

by concatenating the kill command to the output of the pidof command, it does not work, because the output of the pidof command is empty, even if ps aux has an entry for osmo:

Code: Select all

# ps aux | grep osmo
root     11760  0.0  0.0   6392  2204 pts/0    S+   11:23   0:00 grep osmo
# pidof osmo
# 

this must be probably due to the fact that the program restarts so fast that the pidof command doesn't manage to read its process ID (the process ID changes too fast).
This does not seem to depend on the video driver or hardware in use on my system. It looks like this strange / particular situation made it happen that this application is basically hidden.
May anyone confirm this behaviour, please?

Thanks in advance.

[Federico]

Bump!

So, may anyone tell me anything about this? Is it just me or is this a general issue? Did anyone experience such a strange behaviour?

[amethyst]

Code: Select all

killall osmo
sleep 1
osmo

[Federico]

Thank you Amethyst.

It looks like it worked. I added a script on /root/Startup containing the following code:

Code: Select all

#!/bin/sh
sleep 3
killall osmo
sleep 1
osmo

and now I get the icon on the system tray:

Screenshot(16).png (12.4 KiB) Viewed 438 times

and I can use Osmo normally. This must have to do with the order or speed with which apps are started when the X server starts. Hope this helps anybody with the same issue.

And, also, now the pidof command has output, and the process ID of Osmo doesn't seem to change any more:

Code: Select all

# pidof osmo
5606
# pidof osmo
5606
# pidof osmo
5606
# 

Have a nice day.

[BarryK]

Federico,
Something is wrong in your system.

There is already /root/Startup/osmo_tray

This will cause osmo to start in the tray. It should not flash momentarily on the desktop.

What version of Easy are you running?

Look in /mnt/wkg/.session/root/Startup
-- is there a whiteout file in there, that is causing osmo_tray to be hidden?
if so, delete it and immediately reboot without saving the session.

Have you previously done anything manually with osmo, like install a pet?
Manual changes could mess up how osmo works in Easy.

Also check for other files in .session that might be causing trouble...
/mnt/wkg/.session/root/.osmo or .wh..osmo
/mnt/wkg/.session/usr/bin/osmo
--if exist, delete and reboot without saving.

Also, remove your own script in /root/Startup, it is not needed.

[BarryK]

When I executed:

Code: Select all

# ps aux | grep osmo
root     10224  0.0  0.0   6392  2088 pts/0    S+   11:13   0:00 grep osmo
# kill 10224
bash: kill: (10224) - No such process
# 

I found out that the Osmo process ID is costantly changing:

Code: Select all

# ps aux | grep osmo
root     10531  0.0  0.0   6392  2200 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10535  0.0  0.0   6392  2128 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10538  0.0  0.0   6392  2200 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10541  0.0  0.0   6392  2288 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10545  0.0  0.0   6392  2288 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10560  0.0  0.0   6392  2120 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10563  0.0  0.0   6392  2156 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10567  0.0  0.0   6392  2288 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10570  0.0  0.0   6392  2288 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10588  0.0  0.0   6392  2280 pts/0    S+   11:14   0:00 grep osmo
# ps aux | grep osmo
root     10592  0.0  0.0   6392  2284 pts/0    S+   11:14   0:00 grep osmo
# 

Now: for sure I don't know, but this probably means that the program is in a loop: it costantly restarts.

No, osmo is not in a loop. it is not running at all. The above code is not finding pid of osmo.

I can type anything instead of "osmo":

Code: Select all

# ps aux | grep xyz
root     17315  0.0  0.0   6372  2044 pts/1    S+   17:49   0:00 grep xyz
# ps aux | grep xyz
root     17318  0.0  0.0   6372  2020 pts/1    S+   17:49   0:00 grep xyz
# 

The easiest way to find out if a process is running:

Code: Select all

# pidof osmo
4472
# pidof xyz
# 

[BarryK]

If there doesn't seem to be anything wrong in /mnt/wkg/.session
and you have removed your /root/Startup script,
and after restarting X you don't see osmo icon in the tray,
try starting it manually in a terminal:

Code: Select all

# /root/Startup/osmo_tray

If it appears in the tray, that's good.

The fact that you have reported it flashing up momentarily is interesting. What that means is osmo started, but jwm (the window manager) failed to capture it and put it into the tray. Then osmo immediately died, which is also interesting.

Edit /root/Startup/osmo_tray in geany, and increase the sleep time:

Code: Select all

sleep 4

Then restart X, and hopefully it will then be captured in the tray and not flash up on the screen.

[Federico]

Barry, you know that I'm running v. 5.6.4 now since we have worked on the Nvidia drivers.

I didn't do anything manually with Osmo.

We have been having this Osmo problem for a long time now.
At least I noticed it a long time ago.
The point is that one doesn't need a calendar all the time, so that wasn't really an issue for us.

Furtherly, you know that we are running a heavily modified version of Easy (Dolphin, Okular, KDE etc...).
That's the reason why I asked if it was just me... because it is most probably! It must be the result of some external package I installed in the past for whatever reason.
Anyway, the issue is now solved, and that's what matters.
And now I'm gonna do the checks you told me.
If we find another reason we can delete the additional script I added.
Going do thr checks and report back.

[Federico]

on /mnt/wkg/.session/root/Startup there is a hidden file named .wk.osmo_start and it is empty.
There is also the file .wh.keepassxc_tray, and it also empty. Then there are 5 non-hidden files, which are repetitions of what's already placed on /root/Startup. Among them there is also osmo_tray, containing exactly the same code of the version on /root/Startup.

Yes, Osmo appeared to me briefly yesterday, but it is one in a million: we were already used not to have this app any more, since it had already not been working for a long time.

Going to delete the newly created script and increase the timer as suggested

[Federico]

Yes, I deleted my script and corrected osmo_tray.
I rebooted the system twice and the X server 4 times: I confirm that it's enough to increase the timer on line 9 of the file osmo_tray on /root/Startup to 4 seconds, in order to get Osmo back working perfectly.
But this looks like a bug to me: this doesn't seem to depend on any previous modification I made to my system. Maybe the behaviour changes according to the speed of the hardware? Nevermind.
Anyway,

Thank you.

[BarryK]

Yes, it is very interesting that you need to increase that sleep to 4 seconds.
If your computer is very old hardware and X is taking longer to startup, then maybe I can see the need for longer sleep, but I presume your computer is fairly modern.

Hmmm, no, I have tested Easy on my Compaq Presario, with very old Intel Core 2 cpu, and osmo starts in the tray ok.

So it seems something else is going in your case.

Anyway, I have compromised, changed to "sleep 3".

[Federico]

I bought my laptop in November 2020, at the beginning of the pandemics. It is quite fast for being an ultrabook (Asus Zenbook). It has a quad core Intel Core i5 CPU, with Hyperthreading.
The output of the lscpu command follows:

Code: Select all

# lscpu
Architektur:                       x86_64
  CPU Operationsmodus:             32-bit, 64-bit
  Adressgrößen:                    39 bits physical, 48 bits virtual
  Byte-Reihenfolge:                Little Endian
CPU(s):                            8
  Liste der Online-CPU(s):         0-7
Anbieterkennung:                   GenuineIntel
  Modellname:                      11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Prozessorfamilie:              6
    Modell:                        140
    Thread(s) pro Kern:            2
    Kern(e) pro Sockel:            4
    Sockel:                        1
    Stepping:                      1
    Übertaktung:                   aktiviert
    Maximale Taktfrequenz der CPU: 2401,0000
    Minimale Taktfrequenz der CPU: 400,0000
    BogoMIPS:                      4840.00
    Markierungen:                  fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht t
                                   m pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpui
                                   d aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse
                                   4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault 
                                   epb cat_l2 invpcid_single cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad f
                                   sgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt c
                                   lwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves split_lock_detect dtherm ida arat pl
                                   n pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqd
                                   q avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid movdiri movdir64b fsrm avx512_vp2intersect md_clear flush_l1d a
                                   rch_capabilities
Virtualisierungsfunktionen:        
  Virtualisierung:                 VT-x
Caches (Gesamtsumme):              
  L1d:                             192 KiB (4 Instanzen)
  L1i:                             128 KiB (4 Instanzen)
  L2:                              5 MiB (4 Instanzen)
  L3:                              8 MiB (1 Instanz)
Schwachstellen:                    
  Gather data sampling:            Mitigation; Microcode
  Itlb multihit:                   Not affected
  L1tf:                            Not affected
  Mds:                             Not affected
  Meltdown:                        Not affected
  Mmio stale data:                 Not affected
  Retbleed:                        Not affected
  Spec rstack overflow:            Not affected
  Spec store bypass:               Mitigation; Speculative Store Bypass disabled via prctl and seccomp
  Spectre v1:                      Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:                      Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds:                           Not affected
  Tsx async abort:                 Not affected

It has an Intel Iris Xe video chip. It is not slow, believe me. May the problem be that I have a lot of icons on the desktop? And therefore the X server is slower to start up? I have 81 icons on desktop.