Mako does not display notification, but only sound sometimes.

[OctopusET]

Sometimes, I notice that there is notification sound, but mako does not show notification. I can fix it via killing mako and starting it again.

I'm using ArchLinux with sway-git (6cb69a4), wlroot-git (6cdf843a), and mako (1.6-1)

[KoalaV2]

+1 experiencing the same issue, often after waking from suspend, doing a makoctl reload often "fixes" it.

[llyyr]

Same experience here as well, it only happens after waking from suspend

[nagisa]

makoctl set-mode normal seems to help with this as well.

[Givralix]

I have the same problem, also fixed by restarting mako or running makoctl set-mode normal. When it happens, mako prints no buffer available. It seems like all the buffers in the pool get marked as busy for some reason.

[markstos]

I'm also experiencing this on Arch Linux, I'm running mako by systemd if that matters. I'm using

• sway 1.7
• wlroots 0.15.1
• Linux kernel 5.15.12

I also see " no buffer available" in the logs, but it's much further back in history. It seems mako has gotten stuck again since that logging happened. I'm not certain that loggig is related.

[CameronNemo]

Updating to mako git fixed this issue for me. Anyone else try that?

[kevinoid]

Updating to mako git fixed this issue for me. Anyone else try that?

Same here. I had been losing several notifications per day with corresponding "no buffer available" errors in the logs using mako 1.6 and sway 1.7. After switching to mako 55104d3 on 4/11, I have not observed any such errors.

[CameronNemo]

@emersion three users (including me) can reproduce this with the released version of mako, but not the git tip. I would recommend cutting a release.

[nazarewk]

I'm also having this issue on a Dell Latitude E5470 laptop with sway 1.7, but i've never noticed it on my AMD-based desktop.

The notification popup simply hangs up and stops reacting to anything, i've noticed the log messages when run mako standalone

UPDATE: looks like it also happens on my desktop

[ainola]

@emersion Friendly reminder that it would be nice to get a new release of Mako to fix this issue!

[cespare]

Since the previous comment there have been three releases. Should this be closed?

(I came across this because I was using 1.6 and encountered the bug. Since building from source I haven't seen it.)

[OctopusET]

I think it can be closed after new release