Start time of 25 seconds

[dR3b]

Starting Waybar under Sway takes about 25 seconds. After that everything works fine.

~ » waybar -l debug -c .config/waybar/config
[2021-09-29 15:15:18.915] [info] Resources files: .config/waybar/config, /home/XYZ/.config/waybar/style.css
[2021-09-29 15:15:43.947] [debug] Output detection done: eDP-1 (Unknown 0x07DB 0x00000000)
[2021-09-29 15:15:43.949] [debug] Output detection done: DP-1 (Goldstar Company Ltd LG ULTRAWIDE 0x000054A5)

[2021-09-29 15:15:43.972] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity
[2021-09-29 15:15:43.974] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:15:43.974] [debug] Cmd exited with code 1

** (waybar:1443): WARNING **: 15:15:43.985: gtk-layer-shell v0.6.0 may not work on GTK v3.24.30. If you experience crashes, check https://github.com/wmww/gtk-layer-shell/blob/master/compatibility.md
[2021-09-29 15:15:43.986] [debug] GTK widget tree:
window#waybar.background.top..DP-1:dir(ltr)
  decoration:dir(ltr)
  box.horizontal:dir(ltr)
    box.horizontal.modules-left:dir(ltr)
      widget:dir(ltr)
        box#workspaces.horizontal:dir(ltr)
      widget:dir(ltr)
        label#mode:dir(ltr)
      widget:dir(ltr)
        label#battery:dir(ltr)
      widget:dir(ltr)
        label#backlight:dir(ltr)
      widget:dir(ltr)
        label#mpd:dir(ltr)
    box.horizontal.modules-center:dir(ltr)
      widget:dir(ltr)
        label#clock:dir(ltr)
      widget:dir(ltr)
        label#custom-weather:dir(ltr)
      widget:dir(ltr)
        label#custom-vpn:dir(ltr)
    box.horizontal.modules-right:dir(ltr)
      widget:dir(ltr)
        label#disk:dir(ltr)
      widget:dir(ltr)
        label#cpu:dir(ltr)
      widget:dir(ltr)
        label#memory:dir(ltr)
      widget:dir(ltr)
        label#network:dir(ltr)
      widget:dir(ltr)
        label#temperature:dir(ltr)
      widget:dir(ltr)
        label#pulseaudio:dir(ltr)
      widget:dir(ltr)
        box#tray.horizontal:dir(ltr)


(waybar:1443): GLib-GObject-WARNING **: 15:15:43.986: ../glib/gobject/gsignal.c:2081: type 'GtkWindow' is already overridden for signal id '73'

(waybar:1443): GLib-GObject-WARNING **: 15:15:43.986: ../glib/gobject/gsignal.c:2081: type 'GtkWindow' is already overridden for signal id '72'
[2021-09-29 15:15:43.988] [debug] mpd: Disconnected: enabled interval timer.
[2021-09-29 15:15:43.990] [debug] network: new default route via if2 metric 100
[2021-09-29 15:15:43.990] [debug] network: enp0s31f6, new addr 10.14.1.53/19
[2021-09-29 15:15:43.990] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity
[2021-09-29 15:15:43.992] [debug] GTK widget tree:
window#waybar.background.top.eDP-1.:dir(ltr)
  decoration:dir(ltr)
  box.horizontal:dir(ltr)
    box.horizontal.modules-left:dir(ltr)
      widget:dir(ltr)
        box#workspaces.horizontal:dir(ltr)
      widget:dir(ltr)
        label#mode:dir(ltr)
      widget:dir(ltr)
        label#battery:dir(ltr)
      widget:dir(ltr)
        label#backlight:dir(ltr)
      widget:dir(ltr)
        label#mpd:dir(ltr)
    box.horizontal.modules-center:dir(ltr)
      widget:dir(ltr)
        label#clock:dir(ltr)
      widget:dir(ltr)
        label#custom-weather:dir(ltr)
      widget:dir(ltr)
        label#custom-vpn:dir(ltr)
    box.horizontal.modules-right:dir(ltr)
      widget:dir(ltr)
        label#disk:dir(ltr)
      widget:dir(ltr)
        label#cpu:dir(ltr)
      widget:dir(ltr)
        label#memory:dir(ltr)
      widget:dir(ltr)
        label#network:dir(ltr)
      widget:dir(ltr)
        label#temperature:dir(ltr)
      widget:dir(ltr)
        label#pulseaudio:dir(ltr)
      widget:dir(ltr)
        box#tray.horizontal:dir(ltr)

[2021-09-29 15:15:43.992] [debug] Cmd exited with code 1
[2021-09-29 15:15:43.992] [debug] Received SIGCHLD in signalThread

** (waybar:1443): WARNING **: 15:15:44.130: Status Notifier Item with bus name ':1.7' and object path '/org/ayatana/NotificationItem/nm_applet' is already registered
[2021-09-29 15:15:44.256] [info] Bar configured (width: 3440, height: 28) for output: DP-1
[2021-09-29 15:15:44.257] [info] Bar configured (width: 1920, height: 28) for output: eDP-1
[2021-09-29 15:15:44.969] [debug] mpd: Connected to MPD
[2021-09-29 15:15:44.970] [debug] mpd: Disconnected: disabled interval timer.
[2021-09-29 15:15:44.970] [debug] mpd: Paused: enabled 200 ms periodic timer.
[2021-09-29 15:15:44.989] [debug] mpd: Connected to MPD
[2021-09-29 15:15:44.989] [debug] mpd: Disconnected: disabled interval timer.
[2021-09-29 15:15:44.989] [debug] mpd: Paused: enabled 200 ms periodic timer.
[2021-09-29 15:15:45.172] [debug] mpd: Paused: disabled 200 ms periodic timer.
[2021-09-29 15:15:45.172] [debug] mpd: Idle: watching FD
[2021-09-29 15:15:45.191] [debug] mpd: Paused: disabled 200 ms periodic timer.
[2021-09-29 15:15:45.191] [debug] mpd: Idle: watching FD
[2021-09-29 15:15:48.984] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:15:48.984] [debug] Cmd exited with code 1
[2021-09-29 15:15:48.997] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:15:48.997] [debug] Cmd exited with code 1
[2021-09-29 15:15:53.993] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:15:53.993] [debug] Cmd exited with code 1
[2021-09-29 15:15:54.002] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:15:54.002] [debug] Cmd exited with code 1
[2021-09-29 15:15:59.003] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:15:59.003] [debug] Cmd exited with code 1
[2021-09-29 15:15:59.007] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:15:59.007] [debug] Cmd exited with code 1
[2021-09-29 15:16:04.010] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:04.010] [debug] Cmd exited with code 1
[2021-09-29 15:16:04.011] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:04.011] [debug] Cmd exited with code 1
[2021-09-29 15:16:09.019] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:09.019] [debug] Cmd exited with code 1
[2021-09-29 15:16:09.020] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:09.020] [debug] Cmd exited with code 1
[2021-09-29 15:16:14.028] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:14.028] [debug] Cmd exited with code 1
[2021-09-29 15:16:14.028] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:14.028] [debug] Cmd exited with code 1
[2021-09-29 15:16:19.037] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:19.037] [debug] Cmd exited with code 1
[2021-09-29 15:16:19.038] [debug] Cmd exited with code 1
[2021-09-29 15:16:19.038] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:24.047] [debug] Cmd exited with code 1
[2021-09-29 15:16:24.047] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:24.047] [debug] Received SIGCHLD in signalThread
[2021-09-29 15:16:24.047] [debug] Cmd exited with code 1

ARCH Linux, Waybar v0.9.8, Sway 1.6.1, Wayland 1.19.0-1

[dR3b]

Sway-Debug Log:

00:00:01.667 [INFO] [sway/commands.c:257] Handling command 'move scratchpad'
00:00:01.667 [DEBUG] [sway/tree/arrange.c:263] Usable area for ws: 1920x1080@0,0
00:00:01.667 [DEBUG] [sway/tree/arrange.c:293] Arranging workspace '9' at 0.000000, 0.000000
00:00:01.667 [DEBUG] [sway/desktop/transaction.c:398] Transaction 0x556cc8e051e0 committing with 3 instructions
00:00:01.667 [DEBUG] [sway/desktop/transaction.c:294] Applying transaction 0x556cc8e051e0
00:00:01.667 [DEBUG] [sway/tree/container.c:1255] Container 0x556cc8dcc730 entered output 0x556cc8c31dc0
00:00:01.669 [DEBUG] [sway/desktop/transaction.c:398] Transaction 0x556cc8e0d180 committing with 1 instructions
00:00:01.669 [DEBUG] [sway/desktop/transaction.c:294] Applying transaction 0x556cc8e0d180
00:00:01.675 [DEBUG] [sway/desktop/transaction.c:398] Transaction 0x556cc8c45030 committing with 1 instructions
00:00:01.675 [DEBUG] [sway/desktop/transaction.c:294] Applying transaction 0x556cc8c45030
00:00:01.755 [DEBUG] [wlr] [types/wlr_surface.c:743] New wlr_surface 0x556cc8e15d90 (res 0x556cc8e10630)
00:00:01.755 [DEBUG] [wlr] [types/wlr_surface.c:743] New wlr_surface 0x556cc8e1b4c0 (res 0x556cc8e16250)

(nm-applet:1380): Gtk-CRITICAL **: 14:58:45.080: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
00:00:01.878 [DEBUG] [wlr] [types/wlr_surface.c:743] New wlr_surface 0x556cc8e20d90 (res 0x556cc8e211c0)
00:00:01.878 [DEBUG] [wlr] [types/wlr_surface.c:743] New wlr_surface 0x556cc8e21370 (res 0x556cc8e217a0)
00:00:26.705 [DEBUG] [sway/ipc-server.c:153] Event on IPC listening socket
00:00:26.705 [DEBUG] [sway/ipc-server.c:199] New client: fd 99
00:00:26.705 [DEBUG] [sway/ipc-server.c:153] Event on IPC listening socket
00:00:26.705 [DEBUG] [sway/ipc-server.c:199] New client: fd 101
00:00:26.705 [DEBUG] [sway/ipc-server.c:219] Client 101 readable
00:00:26.705 [DEBUG] [sway/ipc-server.c:958] Added IPC reply of type 0x2 to client 101 queue: {"success": true}
00:00:26.705 [DEBUG] [sway/ipc-server.c:535] Client 101 writable
00:00:26.706 [DEBUG] [sway/ipc-server.c:219] Client 99 readable
00:00:26.706 [DEBUG] [sway/ipc-server.c:958] Added IPC reply of type 0x1 to client 99 queue: [ { "id": 4, "type": "workspace", "orientation": "horizontal", "percent": null, "urgent": false, "marks": [ ], "layout": "splith", "border": "none", "current_border_width": 0, "rect": { "x": 0, "y": 0, "width": 1920, "height": 1080 }, "deco_rect": { "x": 0, "y": 0, "width": 0, "height": 0 }, "window_rect": { "x": 0, "y": 0, "width": 0, "height": 0 }, "geometry": { "x": 0, "y": 0, "width": 0, "height": 0 }, "name": "9", "window": null, "nodes": [ ], "floating_nodes": [ ], "focus": [ ], "fullscreen_mode": 1, "sticky": false, "num": 9, "output": "eDP-1", "representation": "H[]", "focused": true, "visible": true }, { "id": 6, "type": "workspace", "orientation": "horizontal", "percent": null, "urgent": false, "marks": [ ], "layout": "splith", "border": "none", "current_border_width": 0, "rect": { "x": 1920, "y": 0, "width": 3440, "height": 1440 }, "deco_rect": { "x": 0, "y": 0, "width": 0, "height": 0 }, "window_rect": { "x": 0, "y": 0, "width": 0, "height": 0 }, "geometry": { "x": 0, "y": 0, "width": 0, "height": 0 }, "name": "1", "window": null, "nodes": [ ], "floating_nodes": [ ], "focus": [ ], "fullscreen_mode": 1, "sticky": false, "num": 1, "output": "DP-1", "representation": null, "focused": false, "visible": true } ]
00:00:26.706 [DEBUG] [sway/ipc-server.c:535] Client 99 writable
00:00:26.706 [DEBUG] [sway/ipc-server.c:153] Event on IPC listening socket
00:00:26.706 [DEBUG] [sway/ipc-server.c:199] New client: fd 103
00:00:26.706 [DEBUG] [sway/ipc-server.c:153] Event on IPC listening socket
00:00:26.706 [DEBUG] [sway/ipc-server.c:199] New client: fd 105
00:00:26.706 [DEBUG] [sway/ipc-server.c:219] Client 105 readable
00:00:26.706 [DEBUG] [sway/ipc-server.c:958] Added IPC reply of type 0x2 to client 105 queue: {"success": true}
00:00:26.706 [DEBUG] [sway/ipc-server.c:535] Client 105 writable

** (waybar:1370): WARNING **: 14:59:09.981: gtk-layer-shell v0.6.0 may not work on GTK v3.24.30. If you experience crashes, check https://github.com/wmww/gtk-layer-shell/blob/master/compatibility.md
00:00:26.748 [DEBUG] [wlr] [types/wlr_surface.c:743] New wlr_surface 0x556cc8e250f0 (res 0x556cc8e064f0)
00:00:26.748 [DEBUG] [wlr] [types/wlr_layer_shell_v1.c:471] new layer_surface 0x556cc8e21d40 (res 0x556cc8e21ea0)
00:00:26.748 [DEBUG] [sway/desktop/layer_shell.c:598] new layer surface: namespace waybar layer 2 anchor 13 size 0x28 margin 0,0,0,0,
00:00:26.748 [DEBUG] [sway/desktop/layer_shell.c:197] Usable area changed, rearranging output
00:00:26.748 [DEBUG] [sway/tree/arrange.c:263] Usable area for ws: 3440x1412@0,28
00:00:26.748 [DEBUG] [sway/tree/arrange.c:293] Arranging workspace '1' at 1920.000000, 28.000000
00:00:26.748 [DEBUG] [sway/desktop/transaction.c:398] Transaction 0x556cc8e03ae0 committing with 1 instructions
00:00:26.748 [DEBUG] [sway/desktop/transaction.c:294] Applying transaction 0x556cc8e03ae0

(waybar:1370): GLib-GObject-WARNING **: 14:59:09.988: ../glib/gobject/gsignal.c:2081: type 'GtkWindow' is already overridden for signal id '73'

(waybar:1370): GLib-GObject-WARNING **: 14:59:09.988: ../glib/gobject/gsignal.c:2081: type 'GtkWindow' is already overridden for signal id '72'
00:00:26.754 [DEBUG] [sway/ipc-server.c:153] Event on IPC listening socket
00:00:26.754 [DEBUG] [sway/ipc-server.c:199] New client: fd 107
00:00:26.754 [DEBUG] [sway/ipc-server.c:153] Event on IPC listening socket
00:00:26.754 [DEBUG] [sway/ipc-server.c:199] New client: fd 109
00:00:26.754 [DEBUG] [sway/ipc-server.c:219] Client 109 readable
00:00:26.754 [DEBUG] [sway/ipc-server.c:958] Added IPC reply of type 0x2 to client 109 queue: {"success": true}
00:00:26.754 [DEBUG] [sway/ipc-server.c:535] Client 109 writable
00:00:26.754 [DEBUG] [sway/ipc-server.c:219] Client 107 readable
00:00:26.754 [DEBUG] [sway/ipc-server.c:958] Added IPC reply of type 0x1 to client 107 queue: [ { "id": 4, "type": "workspace", "orientation": "horizontal", "percent": null, "urgent": false, "marks": [ ], "layout": "splith", "border": "none", "current_border_width": 0, "rect": { "x": 0, "y": 0, "width": 1920, "height": 1080 }, "deco_rect": { "x": 0, "y": 0, "width": 0, "height": 0 }, "window_rect": { "x": 0, "y": 0, "width": 0, "height": 0 }, "geometry": { "x": 0, "y": 0, "width": 0, "height": 0 }, "name": "9", "window": null, "nodes": [ ], "floating_nodes": [ ], "focus": [ ], "fullscreen_mode": 1, "sticky": false, "num": 9, "output": "eDP-1", "representation": "H[]", "focused": true, "visible": true }, { "id": 6, "type": "workspace", "orientation": "horizontal", "percent": null, "urgent": false, "marks": [ ], "layout": "splith", "border": "none", "current_border_width": 0, "rect": { "x": 1920, "y": 28, "width": 3440, "height": 1412 }, "deco_rect": { "x": 0, "y": 0, "width": 0, "height": 0 }, "window_rect": { "x": 0, "y": 0, "width": 0, "height": 0 }, "geometry": { "x": 0, "y": 0, "width": 0, "height": 0 }, "name": "1", "window": null, "nodes": [ ], "floating_nodes": [ ], "focus": [ ], "fullscreen_mode": 1, "sticky": false, "num": 1, "output": "DP-1", "representation": null, "focused": false, "visible": true } ]
00:00:26.754 [DEBUG] [sway/ipc-server.c:535] Client 107 writable
00:00:26.754 [DEBUG] [sway/ipc-server.c:153] Event on IPC listening socket
00:00:26.755 [DEBUG] [sway/ipc-server.c:199] New client: fd 111
00:00:26.755 [DEBUG] [sway/ipc-server.c:153] Event on IPC listening socket
00:00:26.755 [DEBUG] [sway/ipc-server.c:199] New client: fd 113
00:00:26.755 [DEBUG] [sway/ipc-server.c:219] Client 113 readable
00:00:26.755 [DEBUG] [sway/ipc-server.c:958] Added IPC reply of type 0x2 to client 113 queue: {"success": true}
00:00:26.755 [DEBUG] [sway/ipc-server.c:535] Client 113 writable
00:00:26.758 [DEBUG] [wlr] [types/wlr_surface.c:743] New wlr_surface 0x556cc8e22c40 (res 0x556cc85bd830)
00:00:26.758 [DEBUG] [wlr] [types/wlr_layer_shell_v1.c:471] new layer_surface 0x556cc8e24720 (res 0x556cc8db5370)
00:00:26.758 [DEBUG] [sway/desktop/layer_shell.c:598] new layer surface: namespace waybar layer 2 anchor 13 size 0x28 margin 0,0,0,0,
00:00:26.758 [DEBUG] [sway/desktop/layer_shell.c:197] Usable area changed, rearranging output
00:00:26.758 [DEBUG] [sway/tree/arrange.c:263] Usable area for ws: 1920x1052@0,28
00:00:26.758 [DEBUG] [sway/tree/arrange.c:293] Arranging workspace '9' at 0.000000, 28.000000
00:00:26.758 [DEBUG] [sway/desktop/transaction.c:398] Transaction 0x556cc8e03ae0 committing with 1 instructions
00:00:26.758 [DEBUG] [sway/desktop/transaction.c:294] Applying transaction 0x556cc8e03ae0

** (waybar:1370): WARNING **: 14:59:10.235: Status Notifier Item with bus name ':1.6' and object path '/org/ayatana/NotificationItem/nm_applet' is already registered
00:00:29.700 [DEBUG] [sway/commands/bind.c:617] running command for binding: exec swaynag -t warning -m 'You pressed the exit shortcut. Do you really want to exit sway? This will end your Wayland session.' -b 'Yes, exit sway' 'swaymsg exit'
00:00:29.700 [INFO] [sway/commands.c:257] Handling command 'exec swaynag -t warning -m 'You pressed the exit shortcut. Do you really want to exit sway? This will end your Wayland session.' -b 'Yes, exit sway' 'swaymsg exit''
00:00:29.700 [DEBUG] [sway/commands/exec_always.c:50] Executing swaynag -t warning -m 'You pressed the exit shortcut. Do you really want to exit sway? This will end your Wayland session.' -b 'Yes, exit sway' 'swaymsg exit'
00:00:29.709 [DEBUG] [sway/commands/exec_always.c:91] Child process created with pid 1555
00:00:29.709 [DEBUG] [sway/tree/root.c:299] Recording workspace for process 1555
00:00:29.737 [DEBUG] [wlr] [types/wlr_surface.c:743] New wlr_surface 0x556cc8e276e0 (res 0x556cc8e275c0)
00:00:29.737 [DEBUG] [wlr] [types/wlr_surface.c:743] New wlr_surface 0x556cc8e27b10 (res 0x556cc8e25e00)
00:00:29.737 [DEBUG] [wlr] [types/wlr_layer_shell_v1.c:471] new layer_surface 0x556cc8e27f40 (res 0x556cc8e280a0)
00:00:29.737 [DEBUG] [sway/desktop/layer_shell.c:598] new layer surface: namespace swaynag layer 2 anchor 13 size 0x32 margin 0,0,0,0,
00:00:29.737 [DEBUG] [sway/desktop/layer_shell.c:197] Usable area changed, rearranging output
00:00:29.737 [DEBUG] [sway/tree/arrange.c:263] Usable area for ws: 1920x1020@0,60
00:00:29.737 [DEBUG] [sway/tree/arrange.c:293] Arranging workspace '9' at 0.000000, 60.000000
00:00:29.737 [DEBUG] [sway/desktop/transaction.c:398] Transaction 0x556cc85a9600 committing with 1 instructions
00:00:29.737 [DEBUG] [sway/desktop/transaction.c:294] Applying transaction 0x556cc85a9600
00:00:29.738 [DEBUG] [sway/desktop/layer_shell.c:197] Usable area changed, rearranging output
00:00:29.738 [DEBUG] [sway/tree/arrange.c:263] Usable area for ws: 1920x1022@0,58
00:00:29.738 [DEBUG] [sway/tree/arrange.c:293] Arranging workspace '9' at 0.000000, 58.000000
00:00:29.738 [DEBUG] [sway/desktop/transaction.c:398] Transaction 0x556cc8e240d0 committing with 1 instructions
00:00:29.738 [DEBUG] [sway/desktop/transaction.c:294] Applying transaction 0x556cc8e240d0
00:00:30.470 [DEBUG] [sway/input/cursor.c:900] denying request to set cursor from unfocused client
00:00:30.902 [DEBUG] [wlr] [render/swapchain.c:105] Allocating new swapchain buffer
00:00:30.902 [DEBUG] [wlr] [render/gbm_allocator.c:127] Allocated 256x256 GBM buffer (format 0x34325241, modifier 0x0)

[wernerb]

I am experiencing the same for the last week(s) but only on initial boot. When closing/opening after initial startup it is normal speed again.

Initial boot

Oct 02 14:20:15 apollo systemd[823]: Started Highly customizable Wayland bar for Sway and Wlroots based compositors..
Oct 02 14:20:15 apollo waybar[902]: [2021-10-02 14:20:15.643] [info] Resources files: /home/werner/.config/waybar/config, /home/werner/.config/waybar/style.css
Oct 02 14:20:40 apollo waybar[902]: [2021-10-02 14:20:40.678] [debug] Output detection done: eDP-1 (Unknown 0x414D 0x00000000)
Oct 02 14:20:40 apollo waybar[902]: [2021-10-02 14:20:40.680] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity
Oct 02 14:20:40 apollo waybar[902]: [2021-10-02 14:20:40.699] [debug] network: new default route via if2 metric 600
Oct 02 14:20:40 apollo waybar[902]: [2021-10-02 14:20:40.700] [debug] network: wlp0s20f3, new addr 10.10.10.97/24
Oct 02 14:20:40 apollo waybar[902]: gtk-layer-shell v0.6.0 may not work on GTK v3.24.30. If you experience crashes, check https://github.com/wmww/gtk-layer-shell/blob/master/compatibilit>
Oct 02 14:20:40 apollo waybar[902]: [2021-10-02 14:20:40.712] [debug] GTK widget tree:
Oct 02 14:20:40 apollo waybar[902]: window#waybar.background.bottom.eDP-1.:dir(ltr)
...............

When stopping and starting:

Oct 02 14:22:35 apollo systemd[823]: Stopping Highly customizable Wayland bar for Sway and Wlroots based compositors....
Oct 02 14:22:35 apollo systemd[823]: Stopped Highly customizable Wayland bar for Sway and Wlroots based compositors..
Oct 02 14:22:37 apollo systemd[823]: Started Highly customizable Wayland bar for Sway and Wlroots based compositors..
Oct 02 14:22:37 apollo waybar[2113]: [2021-10-02 14:22:37.945] [info] Resources files: /home/werner/.config/waybar/config, /home/werner/.config/waybar/style.css
Oct 02 14:22:37 apollo waybar[2113]: [2021-10-02 14:22:37.950] [debug] Output detection done: eDP-1 (Unknown 0x414D 0x00000000)
Oct 02 14:22:37 apollo waybar[2113]: [2021-10-02 14:22:37.951] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity
Oct 02 14:22:37 apollo waybar[2113]: [2021-10-02 14:22:37.953] [debug] network: new default route via if2 metric 600
Oct 02 14:22:37 apollo waybar[2113]: [2021-10-02 14:22:37.953] [debug] network: wlp0s20f3, new addr 10.10.10.97/24

Something is going wrong in the display detection?

[ordy]

Facing the same issue.

kernel: 5.14.8-arch1-1
sway 1.6.1
waybar 0.9.8-54-g7af6e84 (waybar-git from AUR)

[2021-10-04 18:47:48.014] [info] Using configuration file /home/ordy/.config/waybar/config
[2021-10-04 18:47:48.015] [info] Using CSS file /home/ordy/.config/waybar/style.css
[2021-10-04 18:48:13.047] [debug] Output detection done: VGA-1 (Acer Technologies X223W LAV0C1684034)
[2021-10-04 18:48:13.058] [warning] Waybar has been built without rfkill support.
[2021-10-04 18:48:13.059] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity
[2021-10-04 18:48:13.059] [warning] As using a timezone, some format args may be missing as the date library havn't got a release since 2018.
[2021-10-04 18:48:13.108] [debug] Received SIGCHLD in signalThread
[2021-10-04 18:48:13.108] [debug] Cmd exited with code 0
[2021-10-04 18:48:13.133] [debug] Received SIGCHLD in signalThread
[2021-10-04 18:48:13.133] [debug] Cmd exited with code 0
[2021-10-04 18:48:13.177] [debug] GTK widget tree:
window#waybar.background.top.VGA-1.:dir(ltr)
   ...

[WhyNotHugo]

Same issue here, with sway-master and wlroots-master.

I can't reproduce this when running a nested sway -- only the "real" sway seems to reproduce this.

[dR3b]

Today i saw some "gnome-keyring" and "xdg-desktop-portal-wlr" errors in journalctl:

Oct 06 06:51:35 xyz gnome-keyring-daemon[1514]: couldn't access control socket: /run/user/1000/keyring/control: File or directory not found
Oct 06 06:51:35 xyz gnome-keyring-d[1514]: couldn't access control socket: /run/user/1000/keyring/control: File or directory not found
Oct 06 07:45:51 xyz gnome-keyring-daemon[1713]: couldn't access control socket: /run/user/1000/keyring/control: File or directory not found
Oct 06 07:45:51 xyz gnome-keyring-d[1713]: couldn't access control socket: /run/user/1000/keyring/control: File or directory not found
Oct 06 19:46:43 xyz gnome-keyring-daemon[1660]: couldn't access control socket: /run/user/1000/keyring/control: File or directory not found
Oct 06 19:46:43 xyz gnome-keyring-d[1660]: couldn't access control socket: /run/user/1000/keyring/control: File or directory not found


Oct 06 06:51:35 xyz dbus-daemon[1185]: [session uid=1000 pid=1185] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.wlr' unit='xdg-desktop-portal-wlr.service' requested by ':1.17' (uid=1000 pid=1257 comm="/usr/lib/xdg-desktop-portal ")
Oct 06 06:51:35 xyz xdg-desktop-portal-wlr[1509]: 2021/10/06 06:51:35 [ERROR] - config: no config file found
Oct 06 06:51:35 xyz dbus-daemon[1185]: [session uid=1000 pid=1185] Activating service name='org.freedesktop.secrets' requested by ':1.17' (uid=1000 pid=1257 comm="/usr/lib/xdg-desktop-portal ")
Oct 06 06:52:05 xyz xdg-desktop-por[1257]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Oct 06 07:43:01 xyz xdg-desktop-por[1288]: Error reading events from display: Data transfer interrupted (broken pipe)
Oct 06 07:43:01 xyz systemd[1140]: xdg-desktop-portal-wlr.service: Main process exited, code=exited, status=1/FAILURE
Oct 06 07:43:01 xyz xdg-desktop-portal-wlr[1509]: 2021/10/06 07:43:01 [ERROR] - wl_display_dispatch failed: Data transfer interrupted (broken pipe)
Oct 06 07:43:01 xyz systemd[1140]: xdg-desktop-portal-wlr.service: Failed with result 'exit-code'.
Oct 06 07:43:01 xyz systemd[1140]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Oct 06 07:43:01 xyz systemd[1140]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Oct 06 07:43:01 xyz systemd[1140]: xdg-desktop-portal-wlr.service: Scheduled restart job, restart counter is at 1.

I have decided to delete the following packages sudo pacman -Rcnsu gnome-keyring:

• gnome-keyring
  • xdg-desktop-portal-gtk

No more errors so far! Everything works as expected!

[ordy]

Good call, removing xdg-desktop-portal-gtk and gnome-keyring fixed it for me as well.

[WhyNotHugo]

Odd. Any idea how either of these interplay with waybar? I use both applications, so not looking forward to just uninstalling them.

[dron1885]

Same issue here. First start of waybar takes 20 seconds:
Output of waybar -l debug:

[2021-10-07 20:25:11.963] [info] Resources files: .config/waybar/config, .config/waybar/style.css
[2021-10-07 20:25:31.720] [debug] Output detection done: DP-2 (Goldstar Company Ltd LG ULTRAGEAR 103NTZN79421)
[2021-10-07 20:25:31.721] [debug] Output detection done: DP-3 (Unknown 2590G4 0x00002472)
[2021-10-07 20:25:31.725] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity
[2021-10-07 20:25:31.776] [debug] GTK widget tree:
window#waybar.background.left.DP-2.:dir(ltr)
  decoration:dir(ltr)
  box.vertical:dir(ltr)
    box.vertical.modules-left:dir(ltr)
      widget:dir(ltr)
        box#workspaces.vertical:dir(ltr)
      widget:dir(ltr)
        label#mode:dir(ltr)
    box.vertical.modules-center:dir(ltr)
      widget:dir(ltr)
        label#window:dir(ltr)
    box.vertical.modules-right:dir(ltr)
      widget:dir(ltr)
        label#custom-clipboard:dir(ltr)
      widget:dir(ltr)
        label#custom-layout:dir(ltr)
      widget:dir(ltr)
        label#idle_inhibitor:dir(ltr)
      widget:dir(ltr)
        box#tray.vertical:dir(ltr)
      widget:dir(ltr)
        label#pulseaudio:dir(ltr)
      widget:dir(ltr)
        label#cpu:dir(ltr)
      widget:dir(ltr)
        label#memory:dir(ltr)
      widget:dir(ltr)
        label#clock:dir(ltr)
[2021-10-07 20:25:32.155] [info] Bar configured (width: 1920, height: 50) for output: DP-3
[2021-10-07 20:25:32.156] [info] Bar configured (width: 60, height: 1080) for output: DP-2

Basically, all hanging is before 'Output detection done'.

I don't have either xdg-desktop-portal-gtk or gnome-keyring installed, so removing them is not an option. Also doesn't seem that I have any errors regarding xdg-desktop-portal.

[oscarpax]

FWIW, removing xdg-desktop-portal-wlr and xdg-desktop-portal did the trick for me. I did not have to remove gnome-keyring

[ordy]

Personnaly, I need an instance of xdg-desktop-portal to run flatpak, I have no issues with xdg-desktop-portal-wlr only with the gtk one (startup hangs even if I keep both).

Can confirm that having gnome-keyring or not with the wlr portal makes no difference.

[dron1885]

Ok guys, for me it was xdg-desktop-portal-kde.
It seems if you have installed more than one the problem will show itself.

[ordy]

Just tried with xdg-desktop-portal-kde. And it has the same issue as xdg-desktop-portal-gtk.

Regardless of beeing installed side by side with xdg-desktop-portal-wlr or as the only portal, it still gave me that same 25s delay.

[jinnko]

Similar issue here as @ordy - would like to use flatpak, and that depends on xdg-desktop-portal, which in turn depends on xdg-desktop-portal-wlr. I have no gnome-keyring or any other variant of xdg-desktop-portal-*. Am seeing the 25s delay before waybar starts.

Can I run a debug build to capture some data that might help find the source of the startup delay?

[0xC0ncord]

It seems this is caused when you have multiple portals running at the same time. What I had to do to fix this was disable portals that are not relevant to my desktop. As a sway user, I only care about xdg-desktop-portal-wlr, so the solution for me was the following:

$ systemctl --user disable --now xdg-desktop-portal-gtk
$ systemctl --user mask xdg-desktop-portal-gtk

I did not have xdg-desktop-portal-kde installed, but if I did I probably would need to do the same for xdg-desktop-portal-kde.

[WhyNotHugo]

I need the wlr portals for screencasting, but use the gtk one for some gtk functionality on Flatpak apps. While the workaround works, it's not practical in my setup.

[Hubro]

I have gnome-keyring, xdg-desktop-portal and xdg-desktop-portal-wlr, and I use them all actively. I can't just uninstall them 😕

This is a huge pain in the ass, because since the tray is not available when my other applications start, they all start without tray icons. This is especially frustrating with Dropbox.

[cst152]

It started up fine for me after I masked thunar.service

systemctl --user mask thunar.service

But damn, what a debug session :D

[Hubro]

@cst152 Are you sure? Have you rebooted and started everything from scratch to verify?

I don't even have thunar installed 🙁

[cst152]

Rebooted twice and it's working flawlessly. Seems like you have something else that causes a timeout, though. Nothing to mask if there is no thunar installed.

[jinnko]

I've figured this out now too. Looks like it was blocking on startup retries of the xdg-desktop-portal-wlr user service.

tl;dr: Replacing pulseaudio with pipewire resolved the issue for me on ArchLinux

This is how I figured it out, hopefully it'll help someone else dig into other variations.

1. Checked what xdg-desktop-portal I had with:

   $ systemctl --user | grep xdg-desktop-portal
     xdg-desktop-portal-wlr.service       loaded active failed   Portal service (wlroots implementation)
     xdg-desktop-portal.service           loaded active running   Portal service
   

2. Noticing the xdg-desktop-portal-wlr service was in a failed state, I checked the logs

   $ journalctl --user -u xdg-desktop-portal-wlr.service
   Oct 20 14:18:21 laptop systemd[711]: Starting Portal service (wlroots implementation)...
   Oct 20 14:18:21 laptop xdg-desktop-portal-wlr[972]: 2021/10/20 14:18:21 [ERROR] - config: no config file found
   Oct 20 14:18:21 laptop xdg-desktop-portal-wlr[972]: 2021/10/20 14:18:21 [ERROR] - pipewire: couldn't connect to context
   Oct 20 14:18:21 laptop xdg-desktop-portal-wlr[972]: 2021/10/20 14:18:21 [ERROR] - xdpw: failed to initialize screencast
   Oct 20 14:18:21 laptop systemd[711]: xdg-desktop-portal-wlr.service: Main process exited, code=exited, status=1/FAILURE
   Oct 20 14:18:21 laptop systemd[711]: xdg-desktop-portal-wlr.service: Failed with result 'exit-code'.
   Oct 20 14:18:21 laptop systemd[711]: Failed to start Portal service (wlroots implementation).
   Oct 20 14:18:21 laptop systemd[711]: xdg-desktop-portal-wlr.service: Scheduled restart job, restart counter is at 1.
   Oct 20 14:18:21 laptop systemd[711]: Stopped Portal service (wlroots implementation).
   

3. Noticed the pipewire failure which seemed like the first thing to explore. I've been putting of replacing pulseaudio for a while, but decided to do it now.

   $ yay -Rcus pulseaudio pulseaudio-bluetooth pulseaudio-equalizer
   

4. Installed pipewire as describe in https://wiki.archlinux.org/title/PipeWire

   $ yay -S pipewire wireplumber pipewire-pulse
   $ systemctl --user enable pipewire.service pipewire.socket pipewire-pulse.service wireplumber.service
   

5. Reboot.

And now waybar starts immediately.

[WhyNotHugo]

Odd, I'm using pipewire and don't have pulseaudio installed. I also don't see any errors in logs for any services. It sounds like all of us have different issues with the same symptom.

[0xC0ncord]

@jinnko I have had Pipewire completely replacing PulseAudio before I had this issue, so I do not think that that is the only solution, but I'm sure it may help others.

Also, since my original comment on how disabling xdg-desktop-portal-gtk worked for me, I can confirm that it does solve the issue with Waybar's delayed startup, however I ended up re-enabling the service because of Flatpaks as you had claimed earlier.

[jinnko]

@WhyNotHugo - have you checked whether there any other failing user services?

   $ systemctl --user | grep fail

@0xC0ncord - indeed, it's evident from discussion so far that there's a variety of causes, hence why I detailed my debugging process in the hope it'll help someone else find their own local variations.

[WhyNotHugo]

I have no failing services.

[cst152]

Running systemctl --user | grep start right after you start sway may help. This should show you services that take a long time to start.

My dear thunar service did start eventually but took a long time starting.

[cst152]

Huh, masking thunar.service didn't work on my other machine. Very niche solution then...

[WhyNotHugo]

I thought the file manager API might be involved, especially since there's been mentions of both nemo and thunar being related.

It seems that GTK tries to communicate with the xdg-desktop-portal, and the portal itself tries to use the File Manager DBus Interface. It's unclear why GTK tries to access the file manager API on initialisation (this seems too eager when it could be later, when it is required).

In my case, there's a timeout after a short while. nemo does provide /usr/share/dbus-1/services/nemo.FileManager1.service which includes Name=org.freedesktop.FileManager1. I suspect that nemo fails to start in time because nemo uses gtk, and gtk tries to access the xdg-desktop-portal, which is still initialising at this point (e.g.: a circular dependency). I'm kinda speculating here though.

Manually pinging the org.freedesktop.FileManager1 D-Bus name does not time out for me (I've yet to try during the 25 second window).

I ran the xdg-desktop-portal with --verbose and confirmed this:

Oct 20 22:16:48 victory xdg-desktop-portal[2324]: XDP: Failed to create FileManager proxy: Error calling StartServiceByName for org.freedesktop.FileManager1: Timeout was reached

Related to this: I've noticed that when running cage via greetd, I get an error message that nemo could not initialised. So it seems that this issue of "GTK tries to communicate with the file manager" is not limited to waybar and actually affecting other applications.

I'm honestly starting to suspect that gtk might be unfit for session-level components like waybar.

[WhyNotHugo]

Looks like this: flatpak/xdg-desktop-portal#636

[cst152]

I thought the file manager API might be involved, especially since there's been mentions of both nemo and thunar being related.

Can confirm. Uninstalling nemo made it work for my other machine.

[WhyNotHugo]

Huh, greetd+gtkgreet show a warning that nemo cannot start.

Seems that it's also related to this: any GTK app will try to run the portal, and, subsequently, a file manager.

[werererer]

I can also confirm this bug and could also solve the problem by uninstalling gnome-keyring & xdg-desktop-portal-gtk

[fuzxi]

At least on my system, this has been fixed in v1:40.0-1.1 of gnome-keyring.

[Hubro]

I fully updated my Arch system today, including gnome-keyring v1:40.0-1, and Waybar is still taking 10+ seconds to launch.

[WhyNotHugo]

@Hubro Yup, this fix needs to be released for this issue to go away. It's unclear when that will happen :(

[tmpm697]

I have exactly problem when suddenly waybar took 10-25s to startup, never happened before.

After for a while I remove xdg-desktop-portal-wlr and waybar startup instantly, so I did install xdg-desktop-portal-wlr before and didn't notice it causes slowness.

Any idea why xdg-desktop-portal-wlr causes problem and a way to fix it? As we might need xdg-desktop-portal-wlr for sharing apps.

[tmpm697]

I observe that installing xdg-desktop-portal-wlr also causing some weirds behavior when I try to set size of swaywm's windows. Does xdg-desktop-portal-wlr takes control of something without users' ack?

[f4iey]

What worked for me was removing xdg-desktop-portal. As I also have a KDE desktop session, only one portal is now running.
I am not planning to screenshare on Sway for now, so it should be okay for me.

[Hubro]

Waybar is no longer starting slowly for me. I assume the previously mentioned fix for xdg-desktop-portal has been released 🙂

[albsch]

I still have the issue. I'm using the default sway config and changed:

• Use swaybar_command waybar

My debug log shows the following:

00:00:01.623 [DEBUG] [sway/config/bar.c:266] Invoking swaybar for bar id 'bar-0'
00:00:01.661 [DEBUG] [sway/config/bar.c:258] Spawned swaybar bar-0
00:00:01.661 [DEBUG] [sway/config.c:673] Running deferred commands
00:00:01.661 [INFO] [sway/commands.c:258] Handling command 'exec systemctl --user import-environment DISPLAY WAYLAND_DISPLAY SWAYSOCK XDG_CURRENT_DESKTOP'
00:00:01.661 [DEBUG] [sway/commands/exec_always.c:46] Executing systemctl --user import-environment DISPLAY WAYLAND_DISPLAY SWAYSOCK XDG_CURRENT_DESKTOP
00:00:01.668 [DEBUG] [sway/commands/exec_always.c:92] Child process created with pid 1266
00:00:01.668 [DEBUG] [sway/tree/root.c:299] Recording workspace for process 1266
00:00:01.668 [INFO] [sway/commands.c:258] Handling command 'exec hash dbus-update-activation-environment 2>/dev/null &&      dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY SWAYSOCK XDG_CURRENT_DESKTOP'
00:00:01.668 [DEBUG] [sway/commands/exec_always.c:46] Executing hash dbus-update-activation-environment 2>/dev/null && dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY SWAYSOCK XDG_CURRENT_DESKTOP
00:00:01.674 [DEBUG] [sway/commands/exec_always.c:92] Child process created with pid 1268
00:00:01.674 [DEBUG] [sway/tree/root.c:299] Recording workspace for process 1268
00:00:01.674 [INFO] [sway/server.c:302] Running compositor on wayland display 'wayland-1'

As far as I can understand, anything dbus related will wait a timeout round if it can't connect to the wayland display correctly (~20 seconds). The log shows that swaybar is started by Sway, and only after that the environment is updated. Could it be that there is a race between Swaybar (which is starting xdg-desktop-portal) and the environment variables updating?

I notice the issue pretty much all the time, and can get rid of it when I reduce the CPU load on start up. I'm using 100% CPU for a few seconds every time sway starts up, and that seems to trigger a race condition. Could this be a general sway issue? Everything should work with the recommended sway setup in the wiki, right?

[MelihDarcanxyz]

Having the exact same issue on river 0.1.3 although sway seem to work nice. Just switched to pipewire and installed xdg-desktop-portal-wlr

[albsch]

I stumbled upon this issue with my i3 setup, too. I finally figured it out, though I can't explain why it works. I singled out the cause to setting the env var XDG_DATA_DIRS in a wrong way in my .config/environment.d folder.

Before:
XDG_DATA_DIRS=${HOME}/.local/bin/${USER}:${HOME}/.local/bin:${XDG_DATA_DIRS}
After:
XDG_DATA_DIRS=${HOME}/.local/bin/${USER}:${HOME}/.local/bin:${XDG_DATA_DIRS}:/usr/local/share/:/usr/share/

Now all my issues concerning startup delay have disappeared, for both my i3 and sway setups. It's a very specific fix, I don't know if it'll help anyone else.