Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#996910: linphone: Segmentation fault when registering a sip account

94 views
Skip to first unread message

Tiago Bortoletto Vaz

unread,
Oct 20, 2021, 12:20:04 PM10/20/21
to
Package: linphone
Version: 4.2.5-3
Severity: important
X-Debbugs-Cc: ti...@debian.org

Dear Maintainer,

I'm getting a segmentation fault every time I try to registar a regular UDP
account from my SIP provider:

[...]
: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
[11:59:09:441][0x55a449eb92b0][Info]app/App.cpp:225: "Creating subwindow: `qrc:/ui/views/App/Settings/SettingsWindow.qml`."
[11:59:09:506][0x55a449eb92b0][Info]app/App.cpp:232: "Subwindow status: `1`."
[11:59:09:682][0x55a449eb92b0][Warning]qrc:/ui/views/App/Settings/SettingsAdvanced.qml:91: qrc:/ui/views/App/Settings/SettingsAdvanced.qml:91:7: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
[11:59:09:911][0x55a449eb92b0][Warning]qrc:/ui/views/App/Settings/SettingsVideo.qml:149: qrc:/ui/views/App/Settings/SettingsVideo.qml:149:7: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
[11:59:09:911][0x55a449eb92b0][Warning]qrc:/ui/views/App/Settings/SettingsVideo.qml:142: qrc:/ui/views/App/Settings/SettingsVideo.qml:142:7: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
[11:59:10:027][0x55a449eb92b0][Warning]app/App.cpp:802: System tray not found on this system.
[11:59:10:062][0x55a449eb92b0][Warning]qrc:/ui/views/App/Main/Assistant/AssistantHome.qml:132: qrc:/ui/views/App/Main/Assistant/AssistantHome.qml:132:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
[11:59:10:236][0x55a449eb92b0][Info]components/core/event-count-notifier/AbstractEventCountNotifier.cpp:71: "Notify event count: 0."
[11:59:20:311][0x55a449eb92b0][Info]components/assistant/AssistantModel.cpp:416: "Set config on assistant: `/usr/share/linphone/assistant/use-other-sip-account.rc`."
Segmentation fault

Thanks,

-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linphone depends on:
ii linphone-desktop 4.2.5-3

linphone recommends no packages.

linphone suggests no packages.

-- no debconf information

Dennis Filder

unread,
Oct 20, 2021, 1:00:02 PM10/20/21
to
X-Debbugs-CC: Tiago Bortoletto Vaz <ti...@debian.org>

On Wed, Oct 20, 2021 at 12:06:05PM -0400, Tiago Bortoletto Vaz wrote:
> Package: linphone
> Version: 4.2.5-3
> Severity: important
> X-Debbugs-Cc: ti...@debian.org
>
> Dear Maintainer,
>
> I'm getting a segmentation fault every time I try to registar a regular UDP
> account from my SIP provider:
>
> [...]
> : Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> [11:59:09:441][0x55a449eb92b0][Info]app/App.cpp:225: "Creating subwindow: `qrc:/ui/views/App/Settings/SettingsWindow.qml`."
> [11:59:09:506][0x55a449eb92b0][Info]app/App.cpp:232: "Subwindow status: `1`."
> [11:59:09:682][0x55a449eb92b0][Warning]qrc:/ui/views/App/Settings/SettingsAdvanced.qml:91: qrc:/ui/views/App/Settings/SettingsAdvanced.qml:91:7: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> [11:59:09:911][0x55a449eb92b0][Warning]qrc:/ui/views/App/Settings/SettingsVideo.qml:149: qrc:/ui/views/App/Settings/SettingsVideo.qml:149:7: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> [11:59:09:911][0x55a449eb92b0][Warning]qrc:/ui/views/App/Settings/SettingsVideo.qml:142: qrc:/ui/views/App/Settings/SettingsVideo.qml:142:7: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> [11:59:10:027][0x55a449eb92b0][Warning]app/App.cpp:802: System tray not found on this system.
> [11:59:10:062][0x55a449eb92b0][Warning]qrc:/ui/views/App/Main/Assistant/AssistantHome.qml:132: qrc:/ui/views/App/Main/Assistant/AssistantHome.qml:132:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> [11:59:10:236][0x55a449eb92b0][Info]components/core/event-count-notifier/AbstractEventCountNotifier.cpp:71: "Notify event count: 0."
> [11:59:20:311][0x55a449eb92b0][Info]components/assistant/AssistantModel.cpp:416: "Set config on assistant: `/usr/share/linphone/assistant/use-other-sip-account.rc`."
> Segmentation fault

When you try to register the account, what steps to you go through? I
presume in the main window you're clicking in this order: Home ->
Assistant -> Use a SIP Account. If so, does Linphone still crash if
you omit the "sip:" prefix in the input field "SIP Domain"? That
field must be a resolvable hostname, domain name or an IP address, and
unfortunately the input validation in that dialog is not as good as it
should be.

If the above advice does not resolve the issue, please give detailed
steps on what you click and what information you enter in each field.
Also exit Linphone and then start a new Linphone instance from a
terminal like this:

catchsegv linphone 2>&1 | tee /tmp/linphone-segfault.txt

Then post that file here after it has crashed.

Regards.

Dennis Filder

unread,
Oct 21, 2021, 12:10:05 PM10/21/21
to
X-Debbugs-CC: Tiago Bortoletto Vaz <ti...@debian.org>

On Wed, Oct 20, 2021 at 04:49:33PM -0400, Tiago Bortoletto Vaz wrote:
> Hi, thanks for the quick answer,
>
> On Wed, Oct 20, 2021 at 06:48:43PM +0200, Dennis Filder wrote:
> [...]
>
> > When you try to register the account, what steps to you go through? I
> > presume in the main window you're clicking in this order: Home ->
> > Assistant -> Use a SIP Account. If so, does Linphone still crash if
> > you omit the "sip:" prefix in the input field "SIP Domain"? That
> > field must be a resolvable hostname, domain name or an IP address, and
> > unfortunately the input validation in that dialog is not as good as it
> > should be.
>
> Yes, it crashes when I use a domain name without "sip:" prefix.

What domain name are you using? Also are you doing this from the same
dialog as before? Because from the log output I would guess you are
using the settings menu instead of the account registering dialog.
Whether a crash happens from within the settings menu that would also
be important to know. Also, are you running Orca by any chance?

> > If the above advice does not resolve the issue, please give detailed
> > steps on what you click and what information you enter in each field.
> > Also exit Linphone and then start a new Linphone instance from a
> > terminal like this:
> >
> > catchsegv linphone 2>&1 | tee /tmp/linphone-segfault.txt
> >
> > Then post that file here after it has crashed.
>
> Sure, attached.
>
> Let me know if there is anything else I can do to help.

That was not as illuminating as I had hoped. If you can, download the
debug symbols package for linphone-desktop (or wherever the segfault
happens) from
http://debug.mirrors.debian.org/debian-debug/pool/main/l/linphone-desktop/
and run it under gdb to get a stack trace.

Regards.

Tiago Bortoletto Vaz

unread,
Dec 28, 2021, 9:50:02 AM12/28/21
to
>
> What domain name are you using? Also are you doing this from the same
> dialog as before? Because from the log output I would guess you are
> using the settings menu instead of the account registering dialog.
> Whether a crash happens from within the settings menu that would also
> be important to know. Also, are you running Orca by any chance?

I've tried available subdomains from voip.ms provider. For instance,
vancouver1.voip.ms. I'm entering the registration data via the registering
dialog, the one which appears once we open Linphone for the first time. I've
also tried using the Preferences -> SIP accounts menu and get this segfault.
I'm not running Orca.

[...]

> That was not as illuminating as I had hoped. If you can, download the
> debug symbols package for linphone-desktop (or wherever the segfault
> happens) from
> http://debug.mirrors.debian.org/debian-debug/pool/main/l/linphone-desktop/
> and run it under gdb to get a stack trace.

gdb log attached. I hope that can be useful :\

Bests,

--
Tiago
gdb.txt

Dennis Filder

unread,
Dec 28, 2021, 12:40:04 PM12/28/21
to
X-Debbugs-CC: Tiago Bortoletto Vaz <ti...@debian.org>

On Tue, Dec 28, 2021 at 09:45:04AM -0500, Tiago Bortoletto Vaz wrote:
> gdb log attached. I hope that can be useful :\

That stacktrace looks very similar to the ones from #983597 which
already has 3 entries in the Qt bugtracker[0] one of which has an
Orca-less reproducer. Thus I'm inclined to mark this as a duplicate.

Unfortunately, tracking this down would probably require unoptimized
debug builds of most of the involved libraries, so that's something
the Qt devs have to solve.

Regards.

0: https://bugreports.qt.io/browse/QTBUG-84858

Tiago Bortoletto Vaz

unread,
Dec 29, 2021, 9:00:03 AM12/29/21
to
On Tue, Dec 28, 2021 at 06:21:56PM +0100, Dennis Filder wrote:
> X-Debbugs-CC: Tiago Bortoletto Vaz <ti...@debian.org>
>
> On Tue, Dec 28, 2021 at 09:45:04AM -0500, Tiago Bortoletto Vaz wrote:
> > gdb log attached. I hope that can be useful :\
>
> That stacktrace looks very similar to the ones from #983597 which
> already has 3 entries in the Qt bugtracker[0] one of which has an
> Orca-less reproducer. Thus I'm inclined to mark this as a duplicate.

That's fine. I'll keep an eye and try to provide them with some info if needed.
By the way, it doesn't depend on the domain, neither it gets to the auth step.

> Unfortunately, tracking this down would probably require unoptimized
> debug builds of most of the involved libraries, so that's something
> the Qt devs have to solve.

Sure, thanks for the investigation.

Bests,
0 new messages