You are not logged in.
System is fully up to date and had at first thought it was a kernel issue. Basically on starting Sway, Waybar and Firefox take around a minute to appear. Telegram-desktop refuses to start. If I load xorg-xwayland package issue everything works fine.
log file for sway does not show any real errors.
Wondering if anyone else is having problems with Sway running pure wayland?
I start sway via .bash_profile
# If running from tty1 start sway
[ "$(tty)" = "/dev/tty1" ] && exec sway -V > ~/.config/sway/sway.log 2>&1 Last edited by Mr Green (2023-07-26 18:06:53)
Mr Green
Offline
Do you meet the requirements pointed out in the blue note in https://wiki.archlinux.org/title/Sway#Configuration
pacman -Qs portalOffline
pacman -Qs portal
local/xdg-desktop-portal 1.16.0-3
Desktop integration portals for sandboxed apps
local/xdg-desktop-portal-kde 5.27.6-1 (plasma)
A backend implementation for xdg-desktop-portal using Qt/KF5include statement in sway config is present... as is 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 XDG_CURRENT_DESKTOP
exec hash dbus-update-activation-environment 2>/dev/null && \
dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY SWAYSOCK XDG_CURRENT_DESKTOPSway was fine up a couple of kernel updates ago so about a week then this started to happen. Have tried a number of kernels to see it was the issue but no change. i3 [xorg] works fine.... wondering if it is related to systemd.
Last edited by Mr Green (2023-07-26 16:13:10)
Mr Green
Offline
Check the system journal for suspicious entries during the delay, my gut and the xwayland situation say that it's probably portal related (and the kde implementation not working on native wayland)
Might also be a notification daemon issue.
Otherwise we'll have to check dbus-monitor and finaly "strace -f -tt"
Offline
Will do ;-) ... after some searching found that I have this error...
systemctl --user status xdg-desktop-portal.service
× xdg-desktop-portal.service - Portal service
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static)
Active: failed (Result: timeout) since Wed 2023-07-26 17:55:34 BST; 28s ago
Process: 3267 ExecStart=/usr/lib/xdg-desktop-portal (code=killed, signal=TERM)
Main PID: 3267 (code=killed, signal=TERM)
CPU: 19ms
Jul 26 17:54:04 arch systemd[699]: Starting Portal service...
Jul 26 17:54:29 arch xdg-desktop-por[3267]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Timeout was reached
Jul 26 17:54:29 arch xdg-desktop-por[3267]: No skeleton to export
Jul 26 17:55:34 arch systemd[699]: xdg-desktop-portal.service: start operation timed out. Terminating.
Jul 26 17:55:34 arch systemd[699]: xdg-desktop-portal.service: Failed with result 'timeout'.
Jul 26 17:55:34 arch systemd[699]: Failed to start Portal service.Wondered if it is related to this:
https://bbs.archlinux.org/viewtopic.php?id=285590
Did have xdg-dkestop-portal-kde installed but even after removing it error remains.
Mr Green
Offline
Well was looking at xdg-desktop-portal-gnome package and it loads wayland-protocols
So installed it and now sway runs fine again, waybar starts and telegram fires up....
Will have to do some reading as to why it works now.... will mark as solved for now!
Thank you so much for your help ;-)
Last edited by Mr Green (2023-07-26 18:07:24)
Mr Green
Offline
nb. that xdg-desktop-portal-gnome has recently shown up to cause the exact same symptoms you describe outside of gnome sessions.
You might want ot try xdg-desktop-portal-gtk instead and if you don't use flatpak, you might not need any xdg-desktop-portal whatsoever.
Offline
pacman -Qi xdg-desktop-portal
Name : xdg-desktop-portal
Version : 1.16.0-3
Description : Desktop integration portals for sandboxed apps
Architecture : x86_64
URL : https://github.com/flatpak/xdg-desktop-portal
Licenses : LGPL
Groups : None
Provides : None
Depends On : fuse3 gdk-pixbuf2 geoclue glib2 pipewire rtkit systemd xdg-desktop-portal-impl
Optional Deps : None
Required By : cura-bin
Optional For : firefox telegram-desktop
Conflicts With : None
Replaces : None
Installed Size : 2006.11 KiB
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date : Thu 11 May 2023 17:42:35 BST
Install Date : Wed 26 Jul 2023 17:03:04 BST
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By : SignatureFound the culprit, aka User Error!
Will remove cura and then xdg-desktop-portal ;-)
sudo pacman -Rs cura-bin
checking dependencies...
:: firefox optionally requires xdg-desktop-portal: Screensharing with Wayland
:: pipewire optionally requires rtkit: realtime privileges with rtkit module
:: telegram-desktop optionally requires xdg-desktop-portal: desktop integration
Packages (4) geoclue-2.7.0-1 rtkit-0.13-2 xdg-desktop-portal-1.16.0-3 cura-bin-5.4.0-1
Total Removed Size: 635.53 MiB
:: Do you want to remove these packages? [Y/n] y
:: Processing package changes...
(1/4) removing cura-bin [########################################] 100%
(2/4) removing xdg-desktop-portal [########################################] 100%
(3/4) removing rtkit [########################################] 100%
(4/4) removing geoclue [########################################] 100%
:: Running post-transaction hooks...
(1/4) Reloading system manager configuration...
(2/4) Arming ConditionNeedsUpdate...
(3/4) Reloading system bus configuration...
(4/4) Updating the desktop file MIME type cache...Last edited by Mr Green (2023-07-27 14:11:45)
Mr Green
Offline