[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=485719

--- Comment #2 from jresch95 at 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 "\n        INSERT INTO Messages (\n            id,\n        
   phoneNumber,\n            text,\n            time,\n            read,\n     
      delivered,\n            sentByMe,\n            attachments,\n           
smil,\n            fromNumber,\n            messageId,\n           
deliveryReport,\n            readReport,\n            pendingDownload,\n       
    contentLocation,\n            expires,\n            size)\n        VALUES
(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\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 the assignee for the bug.