Right modules aren't displaying after installation

[gigsoll]

Describe the bug After installation by instruction in README.md modules "dashboard", "workspaces", "windowtitle" aren't displaying

To Reproduce

1. Install dotfiles
2. Run ags in a terminal

Expected behavior modules "dashboard", "workspaces", "windowtitle" are displaying

Screenshots

Desktop (please complete the following information):

• Distribution: Arch Linux
• Window manager: Hyprland v0.41.2

Additional context Console output when ags is launched

(com.github.Aylur.ags:11874): Gjs-Console-WARNING **: 20:10:24.935: Another notification daemon is already running: SwayNotificationCenter

(com.github.Aylur.ags:11874): Gjs-Console-CRITICAL **: 20:10:25.180: Could not find monitor with id: 2

(com.github.Aylur.ags:11874): Gjs-CRITICAL **: 20:10:25.235: JS ERROR: TypeError: wsRules[currentMonitorName] is undefined
getWorkspacesForMonitor@file:///tmp/ags/hyprpanel/main.js:1138:5
Workspaces/<.component<.children</<@file:///tmp/ags/hyprpanel/main.js:1227:18
Workspaces/<.component<.children<@file:///tmp/ags/hyprpanel/main.js:1222:41
update@resource:///com/github/Aylur/ags/utils/binding.js:4:28
merge@resource:///com/github/Aylur/ags/utils/binding.js:5:34
Workspaces@file:///tmp/ags/hyprpanel/main.js:1221:23
workspaces@file:///tmp/ags/hyprpanel/main.js:1785:39
Bar/setup/</self2.children<@file:///tmp/ags/hyprpanel/main.js:1814:120
Bar/setup/<@file:///tmp/ags/hyprpanel/main.js:1814:100
hook/<@resource:///com/github/Aylur/ags/widgets/widget.js:43:25
_init/GLib.MainLoop.prototype.runAsync/</<@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266:34

(com.github.Aylur.ags:11874): Gjs-CRITICAL **: 20:10:34.560: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was destroy on Ags_Box 0x5b793451e950.
== Stack trace for context 0x5b7933466200 ==
#0   5b793352e198 i   resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266 (25396f47d560 @ 139)

(com.github.Aylur.ags:11874): Gjs-CRITICAL **: 20:10:34.560: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was destroy on Ags_Label 0x5b793380f480.
== Stack trace for context 0x5b7933466200 ==
#0   5b793352e198 i   resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266 (25396f47d560 @ 139)

(com.github.Aylur.ags:11874): Gjs-CRITICAL **: 20:10:34.560: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was destroy on Ags_Label 0x5b793380f480.
== Stack trace for context 0x5b7933466200 ==
#0   5b793352e198 i   resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266 (25396f47d560 @ 139)

[matavach]

Hmmm this looks like AGS isn't connecting to Hyprland.

I can't get this to replicate for me.

My first guess is that SwayNotificationCenter is interfering with it. Can you kill that and try running ags again?

[gigsoll]

It was caused because of not working expose plugin. After you stayed I started to turnoff parts of my config and find it out. Thank for help ❤️❤️❤️

[Jas-SinghFSU]

Hmmm, curious as to why the expose plugin would cause this error

(com.github.Aylur.ags:11874): Gjs-CRITICAL **: 20:10:25.235: JS ERROR: TypeError: wsRules[currentMonitorName] is undefined
getWorkspacesForMonitor@file:///tmp/ags/hyprpanel/main.js:1138:5

That usually happens if a workspace rule is defined for a monitor that doesn't exist - usually a bad hyprland config.