Yes, looks like a regression. I hade phone calls working pretty well until the latest upgrade. Now the ringing continues, even after the calling party hangs up, until I do killall gnome-calls.
I am in the same boat as @guru with 44-alpha, and no older version in /var/cache/apt/archives.
1 Like
I have updated my other L5 which I havenāt used for some weeks. Around ~30 pkg have been update and there Iāve in the archive dir:
purism@pureos:~$ ls -l /var/cache/apt/archives/gnome-calls*
-rw-r--r-- 1 root root 260368 Oct 11 17:31 /var/cache/apt/archives/gnome-calls_43.0-1pureos1_arm64.deb
-rw-r--r-- 1 root root 268132 Dec 11 04:32 /var/cache/apt/archives/gnome-calls_44~alpha.0-1pureos1_arm64.deb
@tomoqv, I could place the 43.0 hidden on my web server. Just contact me with PM.
1 Like
Downgrading to 43.0-1 resolved the problem for me. I must say I find it a bit strange that untested alpha software gets updated through the Purism software store, especially important software like gnome-calls.
6 Likes
Save file
https://damo.math.aegean.gr/~atsol/gnome-calls_43~beta.0-1pureos1_arm64.deb
and then
sudo apt-get install ./gnome-calls_43~beta.0-1pureos1_arm64.deb
+1
(The forum wants at least 10 chars on reply, so here they are)
OK, try
ls -lt /var/log/apt/history.log*
Then, starting with the newest files ā¦
For an uncompressed file
grep packagename file
For a compressed file (.gz)
zcat file | grep packagename
until you find the bad upgrade (which was presumably quite recent and wonāt be hard to find).
New system upgrade available today and the non-working gnome-calls 44~alpha.0-1 lurking to upgrade.
Here is what to do to upgrade everything BUT gnome-calls:
sudo apt-mark hold gnome-calls
sudo apt update && sudo apt upgrade
To restore upgrade of gnome-calls do:
sudo apt-mark unhold gnome-calls
2 Likes
Maybe itās wise to let the update happen and see if the issue was fixed.
People need the phone as a phone. So better upgeade when calls is at least ābetaā and not āalphaā as it is now.
1 Like
We are also somewhat testers of this new phone to help to make the things better. I have installed:
purism@pureos:~$ apt info gnome-calls 2> /dev/null | grep -i version
Version: 44~alpha.0-1pureos1
and until now Iāve not faced anything wrong during the calls I made.
I have newer version and calls v44alpha has serious issues:
`[purism@pureos ~]$ cat /proc/cmdline
u_boot_version=2022.10-gc4960dade2 console=ttymxc0,115200 quiet fsck.repair=yes security=apparmor splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
Sorry, this info about cat /proc/cmdline was a wrong cut&paste. I corrected it already. I wanted to show the version of gnome-calls.
I am holding off for a while. When I tried the alpha version a couple of days ago, it just kept ringing on an incoming call and didnāt stop until killed. That is, however, similar to the problem I had with my other L5 running gnome-calls 43.0 before I switched. Never got any help troubleshooting that one mentioned here (sorry for the subject line, canāt change it). So it might not be a gnome-calls issue, but it is strange to have a similar problem on two different phones with different versions of gnome-calls.
I did two tests right now:
I called my L5 from another phone in the other hand and stopped the calling from this phone, i.e. without picking the call up in the L5.
I called my L5 again, picked up the call in the L5 this time.
In both cases the ringing stopped fine in the moment of hang-up or pick-up.
Ooops, I think it was relating somehowā¦ OK
The other phone was my business iPhone which I have to use for my work to generate some RSA token for VPN, i.e. please donāt blame me 
āowningā this.
For me the 44~alpha did not have this issue all the time. Sometimes it was working flawlessly. Some other times it kept ringing after call pickup. Sometimes (not always) its window crashed although the call continued to be in progress.
So there is no way to test this by just an experiment. The single experiment may pass. Something became unstable when first time 44~aplha was installed. At that time there was a couple of other OS packages installed. Can someone check which were those? Maybe it is true that gnome-calls was not the one that triggered this behavior.
3 Likes
Iāve reported this issue as https://gitlab.gnome.org/GNOME/calls/-/issues/535.
Now I installed the package from https://gitlab.gnome.org/GNOME/calls/-/merge_requests/647. Lets see if the issue is fixed by this
1 Like