| View previous topic :: View next topic |
| Author |
Message |
regox
Tux's lil' helper
Joined: 12 Sep 2021
Posts: 79
|
 Posted: Sun Mar 19, 2023 3:37 pm Post subject: [SOLVED] Slack Desktop Notifications on Sway |
 |
|
Hi,
I have to use Slack for work. As far as I can tell it's an electron app does work very well out of the box. Only problem I am having is that desktop notifications do not work. I use Sway and dunst as a notification server, issuing notifications manually with "notify-send" works fine.
However if I test the notification feature of Slack, the log says:
| Code: |
(slack:25523): libnotify-WARNING **: 16:28:58.350: Failed to connect to proxy
(slack:25523): libnotify-WARNING **: 16:28:58.350: Failed to connect to proxy
(slack:25523): libnotify-WARNING **: 16:28:58.350: Failed to connect to proxy
[25523:0319/162858.350275:ERROR:libnotify_notification.cc(49)] notify_notification_show: domain=1554 code=13 message="Unknown or unsupported transport “disabled” for address “disabled:”"
[03/19/23, 16:28:58:352] info: Store: NEW_NOTIFICATION {
"id": "xxxxxxxxxxx_xxxxxxxxx.xxxx46",
"title": "[REDACTED]",
"subtitle": "[REDACTED]",
"content": "[REDACTED]",
"authorName": "[REDACTED]",
"avatarImage": "[REDACTED]",
"teamId": "[REDACTED]",
"userId": "[REDACTED]",
"msg": "16792397xx.xxxxxx",
"channel": "[REDACTED]",
"channelName": "[REDACTED]",
"launchUri": "slack://channel?id=xxxxxxxxx&message=xxxxxxxx.xxxx46&team=xxxxxxxxxxxx",
"silent": true,
"hasReply": true
}
|
Is anyone else having a similar problem?
Cheers, regox |
|
| Back to top |
|
 |
regox
Tux's lil' helper
Joined: 12 Sep 2021
Posts: 79
|
| Posted: Sun Mar 19, 2023 4:21 pm Post subject: |
|
|
I was able to fix it, it was a problem with D-Bus, $DBUS_SESSION_BUS_ADDRESS was empty.
Launching sway with "dbus-run-session sway" or setting $DBUS_SESSION_BUS_ADDRESS manually does fix the problem. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22915
|
| Posted: Sun Mar 19, 2023 4:51 pm Post subject: |
|
|
| For reference, Slack can also work in Firefox or Chrome, if you get enough supporting domains unblocked. It's not particularly good about explaining what is broken when it fails to load a resource, but with enough persistence, you can get it to work, and this may be a less bad experience than running a dedicated Electron app to wrap their webapp. |
|
| Back to top |
|
|
CooSee
Veteran
Joined: 20 Nov 2004
Posts: 1477
Location: Earth
|
| Posted: Mon Mar 20, 2023 3:46 pm Post subject: |
|
|
| regox wrote: | I was able to fix it, it was a problem with D-Bus, $DBUS_SESSION_BUS_ADDRESS was empty.
Launching sway with "dbus-run-session sway" or setting $DBUS_SESSION_BUS_ADDRESS manually does fix the problem. |
or, you can edit /usr/share/wayland-sessions/sway.desktop and add dbus-run-session
cat /usr/share/wayland-sessions/sway.desktop
| Code: | [Desktop Entry]
Name=Sway
Comment=An i3-compatible Wayland compositor
Exec=dbus-run-session sway
Type=Application |
it's only reset to default if sway is re-emerged or upgraded.
_________________
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
