Dzhovani Chemishanov 5f281845e0 Fix kdeconnect-cli --list-notifications Returning Nothing ...

## Summary

`kdeconnect-cli --list-notifications` always printed nothing, even when the
paired device had active notifications.

The CLI used `NotificationsModel`: it called `setDeviceId()` and immediately
read `rowCount()`. The model populates its data through asynchronous D-Bus
calls, so at the moment it was read no reply had arrived yet and the model
was always empty.

The fix drops the model from this code path and uses synchronous D-Bus calls
via `DeviceNotificationsDbusInterface` (`activeNotifications()`) and
`NotificationDbusInterface` (`appName()`, `ticker()`), consistent with how
other CLI commands talk to the daemon.

BUG: 440602

## Test Plan

### Before:

1. Pair a device that has at least one active notification (e.g. a missed call).
2. Run `kdeconnect-cli --device <id> --list-notifications`.
3. Observe that nothing is printed, while the same notifications are visible in the app.

### After:

1. Same setup as above.
2. Run `kdeconnect-cli --device <id> --list-notifications`.
3. Each active notification is printed as `- <app name>: <title>`, e.g.:
   `- Phone: Georgi: Missed call`

Verified on Windows 11 (Craft/MSVC build) against a paired Android device
with a real missed call notification, and on WSL Linux (Ubuntu 26.04).

## AI Usage

Used AI: Yes (kimi-k3)

2026-08-23 22:45:04 +02:00

..

CMakeLists.txt

Make CMake create a single bundle on macos

2026-01-18 00:24:52 +01:00

kdeconnect-cli.cpp

Fix kdeconnect-cli --list-notifications Returning Nothing

2026-08-23 22:45:04 +02:00

kdeconnect.zsh

Fix passing multiple attachments to the CLI

2020-10-31 14:02:58 +00:00

Messages.sh

Translated sendfileitemaction and the CLI

2014-06-17 22:21:58 +02:00