How do you start the bar? Does it use waybar or eww or something else?

[x-aether-x]

Also how do you run the wallpaper daemon?

[qxb3]

How do you start the bar? Does it use waybar or eww or something else?

really depends on which rice are u currently trying to run. But most rices uses ags. if u trying to rice the groove rice then its ewww.

Also how do you run the wallpaper daemon?

On groove. it uses dunst.
Some of the rices has no notification / popups like the retro one
Most of them uses ags notification daemon so when u ran the bar / widgets it should run the daemon automatically. just make sure that u dont have another installed or running notification daemon

[x-aether-x]

I am using the yume rice, and am a bit bad at coding, could you please give me a command to put in. Sorry for the hassle

…

On Thu, 6 Feb 2025 at 5:23 PM, qxb3 ***@***.***> wrote: How do you start the bar? Does it use waybar or eww or something else? really depends on which rice are u currently trying to run. But most rices uses ags <https://github.com/Aylur/ags>. if u trying to rice the groove rice then its ewww. Also how do you run the wallpaper daemon? On groove. it uses dunst. Some of the rices has no notification / popups like the retro one Most of them uses *ags* notification daemon so when u ran the bar / widgets it should run the daemon automatically. just make sure that u dont have another installed or running notification daemon — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BL6SEKWRVBWOIOH56GR7Z7L2OL5XFAVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE2DGMZYHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[x-aether-x]

And it also seems like the command to open the sidebar is not working

…

On Thu, Feb 6, 2025 at 5:25 PM Ben Kennedy ***@***.***> wrote: I am using the yume rice, and am a bit bad at coding, could you please give me a command to put in. Sorry for the hassle On Thu, 6 Feb 2025 at 5:23 PM, qxb3 ***@***.***> wrote: > How do you start the bar? Does it use waybar or eww or something else? > > really depends on which rice are u currently trying to run. But most > rices uses ags <https://github.com/Aylur/ags>. if u trying to rice the > groove rice then its ewww. > > Also how do you run the wallpaper daemon? > > On groove. it uses dunst. > Some of the rices has no notification / popups like the retro one > Most of them uses *ags* notification daemon so when u ran the bar / > widgets it should run the daemon automatically. just make sure that u dont > have another installed or running notification daemon > > — > Reply to this email directly, view it on GitHub > <#10 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/BL6SEKWRVBWOIOH56GR7Z7L2OL5XFAVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE2DGMZYHA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[qxb3]

could u show me the output of ags run

[x-aether-x]

Here is the output $ ags run ** (gjs:2408): CRITICAL **: 17:33:20.019: application.vala:167: <data>:1:0Expected a valid selector (gjs:2408): Gjs-CRITICAL **: 17:33:20.030: JS ERROR: TypeError: this[#emitter] is null ***@***.***:///run/user/1000/ags.js:271:9 ***@***.***:///run/user/1000/ags.js:557:39 ***@***.***:///run/user/1000/ags.js:697:16 ***@***.***:///run/user/1000/ags.js:908:5 ***@***.***:///run/user/1000/ags.js:586:12 ***@***.***:///run/user/1000/ags.js:1041:10 ***@***.***:///run/user/1000/ags.js:1981:25 ***@***.***:///run/user/1000/ags.js:590:10 ***@***.***:///run/user/1000/ags.js:1041:10 ***@***.***:///run/user/1000/ags.js:2006:112 ***@***.***:///run/user/1000/ags.js:256:34 ***@***.***:///run/user/1000/ags.js:256:40 ***@***.***:///run/user/1000/ags.js:265:21 ***@***.***:///run/user/1000/ags.js:534:40 ***@***.***:///run/user/1000/ags.js:697:16 ***@***.***:///run/user/1000/ags.js:854:5 ***@***.***:///run/user/1000/ags.js:586:12 ***@***.***:///run/user/1000/ags.js:1041:10 ***@***.***:///run/user/1000/ags.js:2000:26 ***@***.***:///run/user/1000/ags.js:590:10 ***@***.***:///run/user/1000/ags.js:1041:10 ***@***.***:///run/user/1000/ags.js:2160:25 ***@***.***:///run/user/1000/ags.js:590:10 ***@***.***:///run/user/1000/ags.js:1041:10 ***@***.***:///run/user/1000/ags.js:2259:25 ***@***.***:///run/user/1000/ags.js:590:10 ***@***.***:///run/user/1000/ags.js:1041:10 ***@***.***:///run/user/1000/ags.js:2647:25 ***@***.***:///run/user/1000/ags.js:590:10 ***@***.***:///run/user/1000/ags.js:1041:10 ***@***.***:///run/user/1000/ags.js:2996:29 ***@***.***:///run/user/1000/ags.js:590:10 ***@***.***:///run/user/1000/ags.js:1041:10 ***@***.***:///run/user/1000/ags.js:3286:25 ***@***.***:///run/user/1000/ags.js:3392:16 ***@***.***:///run/user/1000/ags.js:800:15 ***@***.***:///org/gnome/gjs/modules/core/overrides/GLib.js:263:34

…

On Thu, Feb 6, 2025 at 5:31 PM qxb3 ***@***.***> wrote: could u show me the output of ags run — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BL6SEKUGUB5R4W6V2IQTJCT2OL6SLAVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE2TEMRQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[qxb3]

which version of ags are u currently using?

[x-aether-x]

Version 2.3.0 Also I forgot to tell you I have this weird red bar up the top of my screen saying this: config error in file /home/toast/.config/hyprland.conf at line 94: source= globbing error: found no match

…

On Thu, Feb 6, 2025 at 5:40 PM qxb3 ***@***.***> wrote: which version of ags are u currently using? — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BL6SEKROLAKYFXBCAFNAYGL2OL7UXAVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE3DGNJUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[x-aether-x]

There are also some other errors up the top, I'll send a screenshot

…

On Thu, Feb 6, 2025 at 5:41 PM Ben Kennedy ***@***.***> wrote: Version 2.3.0 Also I forgot to tell you I have this weird red bar up the top of my screen saying this: config error in file /home/toast/.config/hyprland.conf at line 94: source= globbing error: found no match On Thu, Feb 6, 2025 at 5:40 PM qxb3 ***@***.***> wrote: > which version of ags are u currently using? > > — > Reply to this email directly, view it on GitHub > <#10 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/BL6SEKROLAKYFXBCAFNAYGL2OL7UXAVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE3DGNJUGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[qxb3]

i think the theme has not been initialized or recognized yet. u could try rebooting / restarting hyprland session,

also check if the theme is there by going on: ~/.local/state/theme and checking the symlinks

[x-aether-x]

This just randomly popped up in my terminal window that I was using too: ***@***.*** ~]$ Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached

…

On Thu, Feb 6, 2025 at 5:45 PM qxb3 ***@***.***> wrote: i think the theme has not been initialized or recognized yet. u could try rebooting / restarting hyprland session, also check if the theme is there by going on: ~/.local/state/theme and checking the symlinks — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BL6SEKSAPWEELL6CJFDEY3D2OMAI7AVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE3TANZYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[x-aether-x]

It looks like the themes are there.

…

On Thu, Feb 6, 2025 at 5:45 PM Ben Kennedy ***@***.***> wrote: This just randomly popped up in my terminal window that I was using too: ***@***.*** ~]$ Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached On Thu, Feb 6, 2025 at 5:45 PM qxb3 ***@***.***> wrote: > i think the theme has not been initialized or recognized yet. u could try > rebooting / restarting hyprland session, > > also check if the theme is there by going on: ~/.local/state/theme and > checking the symlinks > > — > Reply to this email directly, view it on GitHub > <#10 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/BL6SEKSAPWEELL6CJFDEY3D2OMAI7AVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE3TANZYG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[x-aether-x]

Restarting my hyprland session made the background and weird error bar up the top disappear, but the side widget still doesnt work

…

On Thu, Feb 6, 2025 at 5:46 PM Ben Kennedy ***@***.***> wrote: It looks like the themes are there. On Thu, Feb 6, 2025 at 5:45 PM Ben Kennedy ***@***.***> wrote: > This just randomly popped up in my terminal window that I was using too: > ***@***.*** ~]$ Error calling StartServiceByName for > org.freedesktop.Notifications: Timeout was reached > > On Thu, Feb 6, 2025 at 5:45 PM qxb3 ***@***.***> wrote: > >> i think the theme has not been initialized or recognized yet. u could >> try rebooting / restarting hyprland session, >> >> also check if the theme is there by going on: ~/.local/state/theme and >> checking the symlinks >> >> — >> Reply to this email directly, view it on GitHub >> <#10 (comment)>, or >> unsubscribe >> <https://github.com/notifications/unsubscribe-auth/BL6SEKSAPWEELL6CJFDEY3D2OMAI7AVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE3TANZYG4> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

[x-aether-x]

Also what do those errors I got when I run ags run mean?

…

On Thu, Feb 6, 2025 at 6:01 PM Ben Kennedy ***@***.***> wrote: Restarting my hyprland session made the background and weird error bar up the top disappear, but the side widget still doesnt work On Thu, Feb 6, 2025 at 5:46 PM Ben Kennedy ***@***.***> wrote: > It looks like the themes are there. > > On Thu, Feb 6, 2025 at 5:45 PM Ben Kennedy ***@***.***> > wrote: > >> This just randomly popped up in my terminal window that I was using too: >> ***@***.*** ~]$ Error calling StartServiceByName for >> org.freedesktop.Notifications: Timeout was reached >> >> On Thu, Feb 6, 2025 at 5:45 PM qxb3 ***@***.***> wrote: >> >>> i think the theme has not been initialized or recognized yet. u could >>> try rebooting / restarting hyprland session, >>> >>> also check if the theme is there by going on: ~/.local/state/theme and >>> checking the symlinks >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <#10 (comment)>, or >>> unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/BL6SEKSAPWEELL6CJFDEY3D2OMAI7AVCNFSM6AAAAABWSXDRBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZYHE3TANZYG4> >>> . >>> You are receiving this because you authored the thread.Message ID: >>> ***@***.***> >>> >>

[x-aether-x]

I just ran these two lines of code, that I didn't see before in the install:
cd ~/.config/ags
ags bundle app.ts yume

but SUPER+tab still doesn't work.

Tried running ags run but it said that it was already running this time?

[Romeo923]

I had this same issue after recently pulling in the latest changes (was previously using an super old version of yume).
For me, the cause of the issue was in the NetworkButton function in .config/ags/windows/bar/sidebar/home/sections/DesktopControls.tsx
More specifically, the ButtonIcons displaying wifi/ethernet status

To fix it I change

<ButtonIcon
      name="WIRED"
      className="icon"
      icon={bind(network.get_wired()!, "state").as((state) => {
      switch (state) {
         case NetworkService.DeviceState.ACTIVATED:
             return "network-wired-symbolic";
         case NetworkService.DeviceState.DISCONNECTED:
             return "network-wired-disconnected-symbolic";
         case NetworkService.DeviceState.UNKNOWN |
             NetworkService.DeviceState.UNAVAILABLE:
             return "network-wired-no-route-symbolic";
         default:
             return "network-wireless-offline-symbolic";
        }
       })}
    />
</box>

To

<ButtonIcon
      name="WIRED"
      className="icon"
      icon={"network-wired-symbolic"}
    />
</box>

And I did a similar change for the wifi ButtonIcon.
My assumption is that there is some issue with network.get_wired() and network.get_wifi() but I have not yet been able to figure out what.