[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 --- Comment #6 from Josh W --- Yes, I too am using spacebar 24.05 which as you mentioned, per https://invent.kde.org/plasma-mobile/spacebar/-/merge_requests/159 it should be fixed. The original user for that issue mentioned that it fixed the issue for them, and they had also mentioned the specific error they suspected it to be was: futuresql: SQL error: "no such table: Messages Unable to execute statement" I thought these issues might be related, because of these lines in my journalctl output: May 30 19:21:42 pcubed spacebar-daemon[4249]: current (old) database revision 8 May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: Marking migration "2023-05-07-102621_init" as done. May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: SQL error: "UNIQUE constraint failed: __qt_schema_migrations.version Unable to fetch row" May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: Migrations finished I am quite sure the issue is related to futuresql and how spacebar uses it. -- You are receiving this mail because: You are watching all bug changes.
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 --- Comment #5 from jresc...@outlook.com --- Josh, thank you for your input and additional research and troubleshooting. The bug report you linked to is similar, but not quite the same as what I am experiencing. The only notification I receive is a notification that the spacebar-daemon has crashed as soon as I send a test text message to the PinePhone. Interestingly, I can send text messages until an incoming test text message crashes the daemon. I looked at merge request 158 that you referenced. It appears that merge request was rejected in favor of 159, which was merged a few weeks ago and was supposed to resolve the same issue that 158 addressed. The CMakeLists.txt file in the master branch of the spacebar indicates the latest version is 24.05.0. That is the version I have installed from pacman, so I assume the fix from 159 is present in the build I am running. Unfortunately, it does not seem to resolve my issue. However, I do have interesting new developments to report. After building from source with the latest commit to the master branch, and running the daemon in the terminal with /usr/local/lib/libexec/spacebar-daemon as before, I now receive text messages and notifications! Unfortunately, I can only receive them when the spacebar front end is closed. Otherwise, the text message is never received, there is no notification, and the daemon outputs the same message as my previous comment in this thread: futuresql: SQL error: "database is locked Unable to fetch row" Perhaps this database lock conflict is occurring because I am manually running the daemon in the terminal? Maybe it has to be initiated by some other process to work properly in the background? For thoroughness, I applied the changed from merge request 158, and rebuilt it, but had the same result. Have you tried building from source? Do you have the same results as I do? Here is how I built it if you need. Hopefully I remembered everything: I uninstalled the spacebar package: $ sudo pacman -Rsn spacebar I installed the following packages (c-ares is a dependency of spacebar, the other packages are for building): $ sudo pacman -S base-devel cmake extra-cmake-modules git c-ares I followed the build instructions from https://invent.kde.org/plasma-mobile/spacebar: $ git clone https://invent.kde.org/plasma-mobile/spacebar.git $ cd spacebar I tried building with the following command: $ cmake -B build && cmake --build build But I got stuck here: [ 51%] Linking CXX executable ../bin/spacebar-daemon /usr/bin/ld: ../lib/libkTelephonySupport.a(phonenumber.cpp.o): undefined reference to symbol '_ZN4absl12lts_2024011612log_internal21CheckOpMessageBuilderC1EPKc' /usr/bin/ld: /usr/lib/libabsl_log_internal_check_op.so.2401.0.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[2]: *** [daemon/CMakeFiles/spacebar-daemon.dir/build.make:227: bin/spacebar-daemon] Error 1 make[1]: *** [CMakeFiles/Makefile2:1177: daemon/CMakeFiles/spacebar-daemon.dir/all] Error 2 make: *** [Makefile:146: all] Error 2 I resolved the linker error by explicitly adding the following libraries to the target_link_libraries in src/CMakeLists.txt and daemon/CMakeLists.txt: absl_log_internal_check_op absl_log_internal_message Then I built and installed it: $ cmake -B build && cmake --build build $ sudo cmake --install build This is how I run the daemon from the terminal: $ /usr/local/lib/libexec/spacebar-daemon I use the following command to uninstall the package that I built from source: $ sudo xargs rm < build/install_manifest.txt I am increasingly confident that the database lock (futuresql: SQL error: "database is locked Unable to fetch row") is my issue. I still don't know how to fix it, but that appears to be the smoking gun. Perhaps a more experienced developer can produce a fix. -- You are receiving this mail because: You are watching all bug changes.
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 --- Comment #4 from Josh W --- I believe this issue is the same: https://bugs.kde.org/show_bug.cgi?id=479067 That thread mentions a fix at https://invent.kde.org/plasma-mobile/spacebar/-/merge_requests/158/diffs -- You are receiving this mail because: You are watching all bug changes.
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 Josh W changed: What|Removed |Added CC||winchesterjosh...@gmail.com --- Comment #3 from Josh W --- I have this same error. I am using Arch+KDE+Plasma Mobile 6 (not Manjaro) but am also having issues getting texts with spacebar. Sadly, there is no other text messaging application that I am aware of. I had this problem 2 months ago when I updated to Plasma 6, and the solution I came up with then was the laziest possible: sudo pacman -U file:///path/to/old/spacebar.pkg.tar.xz. My texts worked like they had before. I had other issues, and reinstalled the OS again recently and still have this problem. In other words this is from a fresh install from https://github.com/dreemurrs-embedded/Pine64-Arch/releases; I then did a full system upgrade using sudo pacman -Syuu glibc-locales --overwrite /usr/lib/locale/\*/\* --noconfirm I still have this issue, nearly the same as jresch: [alarm@pcubed ~]$ sudo journalctl -b | grep spacebar [sudo] password for alarm: May 30 19:21:42 pcubed spacebar-daemon[4249]: Could not find modem "" May 30 19:21:42 pcubed spacebar-daemon[4249]: current (old) database revision 8 May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: Marking migration "2023-05-07-102621_init" as done. May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: SQL error: "UNIQUE constraint failed: __qt_schema_migrations.version Unable to fetch row" May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: Migrations finished May 30 19:21:48 pcubed spacebar-daemon[4249]: kf.modemmanagerqt: Unknown Mobile Country Code: 0 May 30 19:21:48 pcubed spacebar-daemon[4249]: Country Code: "" May 30 19:21:48 pcubed spacebar-daemon[4249]: Country code is null! Phone numbers may not be interpreted correctly May 30 19:21:48 pcubed spacebar-daemon[4249]: qt.dbus.integration: Could not connect "org.freedesktop.DBus.Properties" to onPropertiesChanged(QString, QVariantMap, QStringList) : May 30 19:21:49 pcubed spacebar-daemon[4249]: country code changed "US" May 30 19:21:49 pcubed spacebar-daemon[4249]: dns: "" May 30 19:21:49 pcubed spacebar-daemon[4249]: interface: "" May 30 19:21:50 pcubed spacebar-daemon[4249]: interface changed: "wwu1i4" May 30 19:21:50 pcubed spacebar-daemon[4249]: bearer connected: true May 30 19:21:50 pcubed spacebar-daemon[4249]: dns4 updated: "198.224.155.135,198.224.153.135" May 30 19:22:31 pcubed spacebar[4390]: kf.coreaddons: The plugin "/usr/lib/qt6/plugins/kpeople/datasource/KPeopleVCard.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed May 30 19:22:31 pcubed spacebar[4390]: futuresql: Running "\nWITH Numbers AS (\nSELECT\nMAX(time) AS maxTime,\nphoneNumber\nFROM Messages\n GROUP BY phoneNumber\n)\nSELECT phoneNumber\n FROM Numbers\nORDER BY maxTime desc\n" May 30 19:22:31 pcubed spacebar[4390]: qrc:/ChatsPage.qml:17:1: QML ChatsPage: Created graphical object was not placed in the graphics scene. May 30 19:22:31 pcubed spacebar[4390]: kf.quickcharts.datasource: ModelSource: Invalid role -1 "color" May 30 19:22:31 pcubed spacebar[4390]: kf.quickcharts.datasource: ModelSource: Invalid role -1 "color" May 30 19:22:37 pcubed drkonqi-coredump-processor[4079]: "/usr/lib/spacebar-daemon" 4246 "/var/lib/systemd/coredump/core.spacebar-daemon.1000.628fc09f3f704dcd9d30dc228b6d651c.4246.171710651700.zst" May 30 19:22:37 pcubed drkonqi-coredump-processor[4079]: "/usr/lib/spacebar-daemon" 4244 "/var/lib/systemd/coredump/core.spacebar-daemon.1000.06b3bc244a9a4ee2a37b50c446361402.4244.171710738900.zst" May 30 19:22:37 pcubed drkonqi-coredump-processor[4079]: "/usr/lib/spacebar-daemon" 4252 "/var/lib/systemd/coredump/core.spacebar-daemon.1000.e812c6ab526a485f9197ec8b894c6151.4252.171710958100.zst" May 30 19:22:37 pcubed drkonqi-coredump-processor[4079]: "/usr/bin/spacebar" 4484 "/var/lib/systemd/coredump/core.spacebar.1000.bbdb1101375c4d59947d745b1a669150.4484.171711075800.zst" May 30 19:22:37 pcubed drkonqi-coredump-launcher[4404]: Unable to find file for pid 4246 expected at "kcrash-metadata/spacebar-daemon.628fc09f3f704dcd9d30dc228b6d651c.4246.ini" May 30 19:22:37 pcubed drkonqi-coredump-launcher[4405]: Unable to find file for pid 4244 expected at "kcrash-metadata/spacebar-daemon.06b3bc244a9a4ee2a37b50c446361402.4244.ini" May 30 19:22:37 pcubed drkonqi-coredump-launcher[4408]: Unable to find file for pid 4252 expected at "kcrash-metadata/spacebar-daemon.e812c6ab526a485f9197ec8b894c6151.4252.ini" May 30 19:22:37 pcubed drkonqi-coredump-launcher[4409]: Unable to find file for pid 4484 expected at
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 Marcus E. W. Germano, IV changed: What|Removed |Added CC||sorucoder+kdebugtracker@pro ||ton.me -- You are receiving this mail because: You are watching all bug changes.
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 --- Comment #2 from jresc...@outlook.com --- I built Spacebar (including spacebar-daemon) from source on the PinePhone to try to get the debug symbols for the aforementioned Qt libraries to populate in the backtrace. That didn't work, so I removed the Spacebar (including spacebar-daemon) package using the following command: $ sudo pacman -Rsn spacebar I then "uninstalled" the files from my previous attempt at building from source: $ sudo xargs rm < build/install_manifest.txt Next, I rebuilt Spacebar from source and installed it again: $ cmake -B build && cmake --build build $ sudo cmake --install build After a reboot of the PinePhone, no more crashing...but also nothing at all. I didn't even get a crash when receiving a message. This was because the spacebar-daemon was no longer being autostarted at boot. So I started it manually with the following command: $ /usr/local/lib/libexec/spacebar-daemon Note that the spacebar-daemon executable location is different when Spacebar is built from source and installed with CMake (/usr/local/lib/libexec/spacebar-daemon) vs installed via pacman (/usr/lib/spacebar-daemon). Fortunately, the process no longer crashes when run in this fashion, but I still can't receive any messages. The console output from manually running the spacebar-daemon appears to offer clues: $ /usr/local/lib/libexec/spacebar-daemon Country Code: "US" qt.dbus.integration: Could not connect "org.freedesktop.DBus.Properties" to onPropertiesChanged(QString, QVariantMap, QStringList) : dns: "192.0.0.1" interface: "wwu1i4" current (old) database revision 8 futuresql: Marking migration "2023-05-07-102621_init" as done. futuresql: SQL error: "UNIQUE constraint failed: __qt_schema_migrations.version Unable to fetch row" futuresql: Migrations finished futuresql: Running "\nINSERT INTO Messages (\nid,\n phoneNumber,\ntext,\ntime,\nread,\n delivered,\nsentByMe,\nattachments,\n smil,\nfromNumber,\nmessageId,\n deliveryReport,\nreadReport,\npendingDownload,\n contentLocation,\nexpires,\nsize)\nVALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n" futuresql: Running "UPDATE Messages SET delivered = ? WHERE id == ?" Failed successfully "PolicyKit authorization failed: not authorized for 'org.freedesktop.ModemManager1.Messaging'" futuresql: SQL error: "database is locked Unable to fetch row" After seeing this line, "futuresql: SQL error: "database is locked Unable to fetch row"", I tried using lsof to see what processes were accessing the database: $ lsof ~/.local/share/spacebar/messages.sqlite There were two processes accessing it - spacebar-daemon, and Spacebar - because I had the spacebar app open. I ended both processes and only restarted the spacebar-daemon manually: $ /usr/local/lib/libexec/spacebar-daemon However, after sending a message to myself, I still did not get the message or a crash. Furthermore, I did not get any meaningful output to the console from the running spacebar-daemon. It is worth mentioning that the hardware should not be the issue here as I have been able to send and receive texts with this device using past versions of Plasma Mobile. I suspect this is merely a temporary Plasma 6 (Qt 6) related regression. I don't know what else to do or try at the moment. Are you experiencing this issue as well? If so, please sanity check my troubleshooting thus far. If you have any ideas or insights, I welcome them and would be happy to test theories. -- You are receiving this mail because: You are watching all bug changes.
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 --- Comment #1 from jresc...@outlook.com --- (In reply to jresch95 from comment #0) > *** >PID: 4017 (spacebar-daemon) >UID: 1000 (alarm) >GID: 1000 (alarm) > Signal: 6 (ABRT) > Timestamp: Thu 2024-04-18 02:00:08 CDT (37min ago) > Command Line: /usr/lib/spacebar-daemon > Executable: /usr/lib/spacebar-daemon > Control Group: > /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.spacebar. > daemon@autostart.service > Unit: user@1000.service > User Unit: app-org.kde.spacebar.daemon@autostart.service > Slice: user-1000.slice > Owner UID: 1000 (alarm) >Boot ID: 1d37ac22056a4591b25f6ac829d570dc > Machine ID: c7db93110f9848fca30e68c835b096a8 > Hostname: danctnix >Storage: > /var/lib/systemd/coredump/core.spacebar-daemon.1000. > 1d37ac22056a4591b25f6ac829d570dc.4017.171342360800.zst (present) > Size on Disk: 1.3M >Message: Process 4017 (spacebar-daemon) of user 1000 dumped core. > > Stack trace of thread 4017: > #0 0xb84c2790 n/a (libc.so.6 + 0x82790) > #1 0xb847b6fc raise (libc.so.6 + 0x3b6fc) > #2 0xb84678b0 abort (libc.so.6 + 0x278b0) > #3 0xb84b633c n/a (libc.so.6 + 0x7633c) > #4 0xb84ccf1c n/a (libc.so.6 + 0x8cf1c) > #5 0xb84d15e0 malloc (libc.so.6 + 0x915e0) > #6 0xb8cb5d38 > _ZN10QArrayData9allocate2EPPS_xNS_16AllocationOptionE (libQt6Core.so.6 + > 0x2b5d38) > #7 0xb8c7a3cc > _ZN7QString11reallocDataExN10QArrayData16AllocationOptionE (libQt6Core.so.6 > + 0x27a3cc) > #8 0xb8c92604 > _ZN9QtPrivate16QStringList_joinEPK5QListI7QStringEPK5QCharx (libQt6Core.so.6 > + 0x292604) > #9 0xb869101c n/a (spacebar-daemon + 0x5101c) > #10 0xb8676044 n/a (spacebar-daemon + 0x36044) > #11 0xb8676878 n/a (spacebar-daemon + 0x36878) > #12 0xb865423c n/a (spacebar-daemon + 0x1423c) > #13 0xb86545e8 n/a (spacebar-daemon + 0x145e8) > #14 0xb865d7ac n/a (spacebar-daemon + 0x1d7ac) > #15 0xb865ddf0 n/a (spacebar-daemon + 0x1ddf0) > #16 0xb8660914 n/a (spacebar-daemon + 0x20914) > #17 0xb86615e0 n/a (spacebar-daemon + 0x215e0) > #18 0xb8bd8170 n/a (libQt6Core.so.6 + 0x1d8170) > #19 0xb8685554 n/a (spacebar-daemon + 0x45554) > #20 0xb868b790 n/a (spacebar-daemon + 0x4b790) > #21 0xb8bd8170 n/a (libQt6Core.so.6 + 0x1d8170) > #22 0xb9fab440 > _ZN12ModemManager14ModemMessaging12messageAddedERK7QStringb > (libKF6ModemManagerQt.so.6 + 0x7b440) > #23 0xb9fadc5c n/a (libKF6ModemManagerQt.so.6 + > 0x7dc5c) > #24 0xb8bd8170 n/a (libQt6Core.so.6 + 0x1d8170) > #25 0xb9fd00b0 n/a (libKF6ModemManagerQt.so.6 + > 0xa00b0) > #26 0xb9fd0ce4 n/a (libKF6ModemManagerQt.so.6 + > 0xa0ce4) > #27 0xb9d2bf08 n/a (libQt6DBus.so.6 + 0x4bf08) > #28 0xb8bcb204 _ZN7QObject5eventEP6QEvent > (libQt6Core.so.6 + 0x1cb204) > #29 0xb8b6f824 > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + > 0x16f824) > #30 0xb8b73c34 > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData > (libQt6Core.so.6 + 0x173c34) > #31 0xb8e5d640 n/a (libQt6Core.so.6 + 0x45d640) > #32 0xb7409ec0 n/a (libglib-2.0.so.0 + 0x69ec0) > #33 0xb740c738 n/a (libglib-2.0.so.0 + 0x6c738) > #34 0xb740cff4 g_main_context_iteration > (libglib-2.0.so.0 + 0x6cff4) > #35 0xb8e5cc84 > _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEvents > FlagEE (libQt6Core.so.6 + 0x45cc84) > #36 0xb8b7d068 > _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + > 0x17d068) > #37 0xb8b78ecc _ZN16QCoreApplication4execEv > (libQt6Core.so.6 + 0x178ecc) > #38 0xb86523ac n/a (spacebar-daemon + 0x123ac) > #39 0xb8467b80 n/a (libc.so.6 + 0x27b80) > #40 0xb8467c60 __libc_start_main (libc.so.6 + > 0x27c60) > #41 0xb8652730 n/a (spacebar-daemon + 0x12730) > > Stack trace of thread 4048: > #0 0xb85204d8 __poll (libc.so.6 + 0xe04d8) > #1 0xb740c6c0 n/a
