Arch Linux User Repository

Hello,

Using: KDE / linphone-desktop-appimage 6.1.2-1

Previously, the application displayed incoming call notifications immediately in an application window. Worked perfectly. I just updated to 6.1.2 through the AUR, and now it is trying to display notifications through what seems to be the desktop UI notification system. The problem is that it takes on the order of 5 seconds for these notifications to pop up for me to answer, all of this time, the call is ringing with no way to answer.

I don't know if this is a common user problem or if its just me for some reason, but if this is commonly experienced, this renders the app almost unusable. If this is a common problem, you may consider reverting to the previous version until the 6.1.3 is released. I am currently using an old version from the developer's download website.

Tks

Thank you, lynix, I did not realize the developer was not the package maintainer.

@coloradoruss: This does not sound like a packaging issue to me, more likely a bug or issue with the software itself. You might want to report it upstream to the Linphone developers.

However I have just noticed there is a v6.1.0 release tag, I'll try to get this package updated. Fingers crossed your issues are fixed with the new version.

I have had 6.0.1 lock up my system three times in the past week. I get and place many calls in a day, and most work fine. Three times, however, I have had it lock up my UI, go into some kind of loop causing my fan to blast full power, and rendering my keyboard and mouse completely non-operational. My apps continue to work, for example, I am on a conference call, and I can continue to talk to my coworkers on the conference while the screen is frozen. However, nothing I can do will make my screen respond to include trying to get to a console to kill the process, unplugging and plugging back in the kb and mouse. Each time, I have had to reboot my computer by killing power and rebooting. Two times, I cut and pasted in a phone number, and I think there may have been a weird, invisible character pasted in. The last time, today, it was a good phone number, and the screen locked up and the fan went full blast mid-call or possibly when the other side hung up.

This doesn't look like a squashfs image. Failed to open squashfs image. but linphone-desktop-appimage-stable is ok.

I'm sorry but I can't seem to reproduce your issue. Package builds and runs fine for me.

The binary also is of the right type:

$ file /opt/appimages/linphone.AppImage 
/opt/appimages/linphone.AppImage: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), static-pie linked, BuildID[sha1]=b15b018a4f56042ad61c2b9e0504773f7da1ac38, stripped

This doesn't look like a squashfs image. Failed to open squashfs image. but linphone-desktop-appimage-stable is ok.

Version 5.2.3-2 works for me too. Thanks!

@lynix: Excellent! I'm glad I could help. The new release builds and runs just fine. It sounds like the debug flag was disabled by default previously, which would explain why it hadn't had to be disabled explicitly in the package, or was it always enabled by default and your machine-local overrides are for other reasons?

@bossi: Excellent, thanks for your work identifying the issue!

Yes, 'debug' is now default in /etc/makepkg.conf. I've got it disabled on all my machines, which explains why I'm not seeing the issue.

I will push a -2 with '!debug' in the PKGBUILD shortly.

I've tracked down what's stripping the binary still, even though !strip is specified as an option in PKGBUILD and it turns out it still is the strip script (/usr/share/makepkg/tidy/strip.sh), which strips the binary down to debug symbols if only !strip is specified, it seems. Also setting !debug fixes the issue (options=(!strip !debug)).

It looks like pacman has had some work done on its debug option recently (https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commits/main), maybe that's where a possible regression was introduced since I'm puzzled it assumes the debug option as a default here.