Freezes on Start in i3wm on Arch Linux about tomato.c HOT 19 CLOSED

Yes, I forgot to mention that I did sudo make install.

from tomato.c.

Got it 👌 No problems now.

from tomato.c.

If have any other problem, just open other issue, I'll be glad to help :)

from tomato.c.

Have you installed all the dependencies?

$ sudo pacman -S base-devel ncurses mpv pkgconf libnotify

looks something is wrong with pipewire, but just to be sure.

from tomato.c.

Yes, I have reinstalled dependencies, but still no help.

from tomato.c.

What happens if you disable SOUNDS and NOISE in config.h?

from tomato.c.

Tried
static const int SOUND = 0;
static const int NOISE = 0;
It didn't work.
I also restored the default i3 config, but nothing happens.

from tomato.c.

(You need to recompile to the changes in config.h take effect)

from tomato.c.

Try commenting MPVTOGGLE = 1 in config.mk too. As then mpv will be completely removed from the app.

from tomato.c.

Did it.

Still freezes.
After like 100 seconds it starts the timer. Weird.

from tomato.c.

Dont switch 1 to 0. Actually comment the MPVTOGGLE = 1 line.

Looks like there's problems with notifications too

from tomato.c.

Ahhh sorry. Did that comment just now. But nothing happens unfortunately

from tomato.c.

What happens when you

$ notify-send test

and when you

$ mpv sounds/dfltnotify.mp3

from tomato.c.

Timeout was reached after like 60s

from tomato.c.

After which command?

from tomato.c.

When $ notify-send test it says Timeout was reached
When $ mpv sounds/dfltnotify.mp3:

 (+) Audio --aid=1 (mp3 2ch 44100Hz)
File tags:
 Artist: FoolBoyMedia
 Comment: Created in Ignite, edited in Audition
AO: [pipewire] 44100Hz stereo 2ch floatp
(Paused) A: 00:00:01 / 00:00:01 (98%)

It played the music until it was paused at 98%

from tomato.c.

Looks like you don't have a notification daemon. Maybe try installing dunst, is a very minimal notification daemon:

$ sudo pacman -S dunst

then run it at background (should add to i3wm startup if works):

$ dunst &

then retry notify-send:

$ notify-send test

from tomato.c.

Ah it works. I just found out about the notification daemon.

$ notify-send test was successful and the timer works but I got this notification when resuming a timer:

CRITICAL: Source ID 112 (or a random number) was not found when attempting to remove it

but the timer is resuming the correct time. Does it matter?

from tomato.c.

Try adding dusnt to the i3wm startup and rebooting your machine.

exec --no-startup-id dunst

from tomato.c.