From 42182939b3ca6fe17f59e9b641b28e941d981eee Mon Sep 17 00:00:00 2001 From: Alistair Findlay Date: Wed, 6 May 2026 17:38:58 +1000 Subject: [PATCH] Fix typo in D-Bus activation error message source string is read-only on weblate, so editing here. --- po/en_GB.po | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/po/en_GB.po b/po/en_GB.po index f37fc321d..f4b5a4e7a 100644 --- a/po/en_GB.po +++ b/po/en_GB.po @@ -408,15 +408,16 @@ msgstr "Failed to reach blueman-manager" #: blueman/main/DBusProxies.py:91 msgid "" -"It seems like blueman-manager could no get activated via D-Bus. A typical " + +"It seems like blueman-manager could not be activated via D-Bus. A typical " "cause for this is a broken graphical setup in the D-Bus activation " -"environment that can get resolved with a call to dbus-update-activation-" +"environment, this can be resolved with a call to dbus-update-activation-" "environment, typically issued from xinitrc (respectively the Sway config or " "similar)." msgstr "" -"It seems like blueman-manager could no get activated via D-Bus. A typical " +"It seems like blueman-manager could not be activated via D-Bus. A typical " "cause for this is a broken graphical setup in the D-Bus activation " -"environment that can get resolved with a call to dbus-update-activation-" +"environment, this can be resolved with a call to dbus-update-activation-" "environment, typically issued from xinitrc (respectively the Sway config or " "similar)."