GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

[burianvlastimil]

Describe the bug
After the manually creating another (I try daily) snapshot, the last line spills some error I don't understand. So, it could be superfluous, or it could be serious, or something in between.

To Reproduce
Steps to reproduce the behavior:

1. as root I launch timeshift-gtk
2. Click on Create (there are already 17 snapshots)
3. Error message -> look at the very last line of the output:

App config loaded: /etc/timeshift/timeshift.json
Mounted '/dev/sdc1' at '/run/timeshift/76985/backup'

------------------------------------------------------------------------------
Creating new snapshot...(RSYNC)
Saving to device: /dev/sdc1, mounted at path: /run/timeshift/76985/backup
Linking from snapshot: 2026-01-08_14-42-22
Syncing files with rsync...
Created control file: /run/timeshift/76985/backup/timeshift/snapshots/2026-01-11_03-34-14/info.json
RSYNC Snapshot saved successfully (157s)
Tagged snapshot '2026-01-11_03-34-14': ondemand
------------------------------------------------------------------------------
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

Expected behavior
no error

Screenshots
screenshot not applicable to this issue

System:

• Linux Distribution Name and Version: LMDE 7 Gigi
• Desktop: Cinnamon
• Timeshift Version: 25.12.4
• Timeshift Mode rsync
• Display Server: X11

Personal note:
Before yesterday's system update, there was no error. So, it is related.

[ygerlach]

Hi,
thanks for your report. I think this error is nothing to worry about. I believe it does not even come from timeshift itself, but from notify-send which is called by timeshift to send you a "Snapshot Done" notification. I guess notify-send had some problem finding the correct session information to send you the notification and threw the error.
Did you get an notification?
Do you have notify-send available? (You can run notify-send hi in a terminal and see if a notification pops up)

You can try running timeshift with the --debug argument to get more information before and after the error and share it here.

[burianvlastimil]

Well, I originally have had notifications disabled, but when enabled, it causes same error. I now think there is some error in LMDE 7, because notify-send hi does nothing. It's like this from the last updates, which happened 3 days ago. So, you may close this issue. Cheers