| 10 Apr 2021 |
 Sumner Evans | Strange. I'll look into that. I never would have thought of that, so now I have something to investigate. | 04:47:18 |
 Emil Karlson | wonder if config.d is being looked at anymore | 04:51:13 |
| Emil Karlson | include /etc/sway/config.d/* | 04:59:08 |
| Emil Karlson | is in my config | 04:59:14 |
| Emil Karlson | so there are quite so many things that might have been broken | 04:59:43 |
| Emil Karlson | just moved things to main conf and it seems to work | 05:33:42 |
| Emil Karlson | maybe include is broken or something | 05:33:50 |
| Emil Karlson | sumner: do you have a way forward with this? | 15:39:32 |
| Emil Karlson | did someone report a bug | 15:39:38 |
|  abigcarrot left the room. | 15:39:41 |
| 11 Apr 2021 |
|  polymerwitch joined the room. | 09:26:00 |
 zimbi | Hi I just noticed that bindsym $mod-v splitv is no longer working on my system, any ideas where to look at? | 11:35:21 |
 cytopyge | No hardware changes? When I attached a second keyboard my caps-as-escape didn't work any longer. After I added the hardware id to my swayrc it worked fine again. | 17:21:03 |
| zimbi | no nothing changed | 19:46:30 |
|  Jaafar joined the room. | 20:21:29 |
| Jaafar left the room. | 20:22:08 |
| 12 Apr 2021 |
| Sumner Evans | In reply to @jkarlson:kapsi.fi
sumner: do you have a way forward with this? Not yet, I probably won't have time to look at this until the weekend. | 04:06:43 |
|  marcel joined the room. | 07:57:29 |
| marcel | Greetings, sorry but I thought I could ask in here about a problem with sddm, sway and an application like chromium, element, thunderbird.
The setup is as follows:
- Enter sddm
- Login, sway starts
- Start chromium (immediatly after opening a terminal)
- Sway crashes and reenters sddm
I got from journal that xdg-desktop-portal-wlr.service failed but later it seems to run.
In fact if I wait some time after sway started the application (chromium) does not crash at all.
I registered some xdg-desktop-portal-wlr error messages:
xdg-desktop-portal-wlr[849]: 2021/04/12 10:14:58 [ERROR] - wl_display_dispatch failed: Broken pipe
xdg-desktop-portal-wlr[1043]: 2021/04/12 10:14:59 [ERROR] - wayland: failed to connect to display
It always is one of them until systemd does not try to restart the unit anymore.
I get that with my config as well as with the default config (in Arch).
Someone saw something like that?
Kind regards.
| 10:36:28 |
| marcel | I know some things have to be done to get the environment. I include a file for that which is included in arch as /etc/sway/config.d/50-systemd-user.conf:
# sway does not set DISPLAY/WAYLAND_DISPLAY in the systemd user environment
# See FS#63021
# Adapted from xorg's 50-systemd-user.sh, which achieves a similar goal.
exec systemctl --user import-environment DISPLAY WAYLAND_DISPLAY SWAYSOCK
exec hash dbus-update-activation-environment 2>/dev/null && \
dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY SWAYSOCK
| 10:38:15 |
| marcel | ah wait maybe I did that, I look into that behaviour for two weeks now 🤣 | 10:39:06 |
| marcel | no it seems to be in the sway package for arch | 10:40:09 |
|  bigfoot joined the room. | 11:38:01 |
|  i1l joined the room. | 14:18:20 |
|  Gordon changed their profile picture. | 22:01:33 |
| 13 Apr 2021 |
|  msavoritias left the room. | 07:46:45 |
| i1l left the room. | 11:56:12 |
| 14 Apr 2021 |
|  iamliterallyabee joined the room. | 04:44:44 |
|  tebra joined the room. | 22:31:57 |
| 16 Apr 2021 |
|  miji joined the room. | 10:12:47 |
