Bug 466469 - kdeconnect-sms crashes (SIGSEGV)
Summary: kdeconnect-sms crashes (SIGSEGV)
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeconnect
Classification: Applications
Component: messaging-application (other bugs)
Version First Reported In: 22.12.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Simon Redman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-26 12:21 UTC by Aaron Blasko
Modified: 2024-04-06 19:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Blasko 2023-02-26 12:21:42 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Run`kdeconnect-sms` or open the desktop file

OBSERVED RESULT
A window pops up and immediatly closes (no rendered content)

EXPECTED RESULT
Should open correctly

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.1.12 (zen)
KDE Plasma Version: - (i3wm)
KDE Frameworks Version: - (i3wm)
Qt Version: 5.15.8 - 6.4.2

ADDITIONAL INFORMATION
program stderr:
```
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "(C) 2018-2022, KDE Connect Team" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "SMS Instant Messaging" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "KDE Connect SMS" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Simon Redman" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Aleix Pol Gonzalez" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Nicolas Fella" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "id" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Select a device" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "message" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Send a message" msgid_plural: "" msgctxt: ""
qrc:/qml/ConversationList.qml:26:9: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
fish: Job 1, 'kdeconnect-sms' terminated by signal SIGSEGV (Address boundary error)
```

running in gdb or valgrind hangs (https://i.imgur.com/jG9hpf7.png)
Comment 1 Simon Redman 2023-02-26 13:59:20 UTC
Does the KDE Crash Handler pop up when you see this?

The wiki has a few other suggestions for how to get the backtrace: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

Unfortunately there's not enough here to do anything with. The chatty warnings are always there (except the i18n errors because I fixed them recently)
Comment 2 Aaron Blasko 2023-02-26 18:03:04 UTC
No crash helper appears after the short-lived window appears.

Here is what I got using the method you reccomended:
```
Core was generated by `kdeconnect-sms'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f115ee15970 in ?? () from /usr/lib/libQt5Widgets.so.5
[Current thread is 1 (Thread 0x7f115a00e880 (LWP 2435013))]
(gdb) bt
#0  0x00007f115ee15970 in  ()
    at /usr/lib/libQt5Widgets.so.5
#1  0x00007f115ee1cd3e in  ()
    at /usr/lib/libQt5Widgets.so.5
#2  0x00007f11501512e8 in  ()
    at /usr/lib/qt/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so
#3  0x00007f115fc4746a in QQuickWindowPrivate::polishItems() () at /usr/lib/libQt5Quick.so.5
#4  0x00007f115fc0233b in  ()
    at /usr/lib/libQt5Quick.so.5
#5  0x00007f115fc032c1 in  ()
    at /usr/lib/libQt5Quick.so.5
#6  0x00007f115e555947 in QWindow::event(QEvent*) ()
    at /usr/lib/libQt5Gui.so.5
#7  0x00007f115ed78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
    at /usr/lib/libQt5Widgets.so.5
#8  0x00007f115e08df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#9  0x00007f115e549804 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libQt5Gui.so.5
#10 0x00007f115e528885 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#11 0x00007f1159b2e8d0 in  ()
    at /usr/lib/libQt5XcbQpa.so.5
#12 0x00007f115d11682b in g_main_context_dispatch ()
    at /usr/lib/libglib-2.0.so.0
#13 0x00007f115d16dcc9 in  ()
    at /usr/lib/libglib-2.0.so.0
#14 0x00007f115d1150e2 in g_main_context_iteration ()
    at /usr/lib/libglib-2.0.so.0
#15 0x00007f115e0d8c6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
    at /usr/lib/libQt5Core.so.5
#16 0x00007f115e0866ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
    at /usr/lib/libQt5Core.so.5
#17 0x00007f115e091219 in QCoreApplication::exec() ()
    at /usr/lib/libQt5Core.so.5
#18 0x000055835c9147b5 in  ()
#19 0x00007f115f83c790 in  () at /usr/lib/libc.so.6
```
Comment 3 Bug Janitor Service 2023-03-13 03:45:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Aaron Blasko 2024-04-05 13:53:45 UTC
this can be closed btw