swaywsr icon indicating copy to clipboard operation
swaywsr copied to clipboard

swaywsr quits randomly

Open kflak opened this issue 4 years ago • 10 comments

Hi,

Just started using your wonderful little utility. There is one problem, though, which is that it tends to just quit for no apparent reason. I haven't been able to link this to any specific process, at first I suspected it might have to do with suspend/resume, but this seems not to be the case. I am running it from sway-config like this:

exec_always  swaywsr --icons awesome --config ~/.config/swaywsr/config.toml --no-names

and my config looks like this:

[icons]
TelegramDesktop = ""
firefox = ""
Spotify = ""
termite = "❯"

[aliases]
qutebrowser = "qb"

Not quite sure where to start, as there is no trace of swaywrs in journalctl nor coredumpctl. Is there a way to turn on debugging/logging?

System: Arch linux 5.6.10-rt5-rt, swaywsr 1.0.0, sway 1.4

kflak avatar May 07 '20 08:05 kflak

hey, first of all thanks for the issue :). I will take a look on this weekend, I have also been experiencing this hehe. I have a suspicion on what it might be but haven't had time to look into it.

pedroscaff avatar May 08 '20 11:05 pedroscaff

about the logs I think it is easier if you just run using the command line and see what happens there, not sure where sway logs things that are executed with exec or exec_always

pedroscaff avatar May 08 '20 11:05 pedroscaff

Feeling honored to post a virgin issue ;-)

So I ran swaywsr in a terminal window, and it survived for most of yesterday before finally dying on me with the error:

Error: invalid type: integer `8388653`, expected a string at line 1 column 724

Hope this helps! Will keep running the program like this for a while to see if the errors stay consistent.

kflak avatar May 09 '20 07:05 kflak

Yet another crash, this time with:

Error: invalid type: integer `12582918`, expected a string at line 1 column 717
``

kflak avatar May 09 '20 09:05 kflak

I did one update, can you please try it again?

pedroscaff avatar May 11 '20 21:05 pedroscaff

Will do! Running it in a terminal now and will let you know if there are any dropouts.

kflak avatar May 12 '20 07:05 kflak

Still getting the same errors. Been updating through aur (swaywsr-git), is this the latest version?

kflak avatar May 13 '20 09:05 kflak

hi, so sorry I didn't get back to you, I missed the notification. I wasn't even aware of the aur pacakge :), from what I have seen it has been last updated on 2020-04-19 06:13, so it should not be the latest version. I will check how to maybe publish on cargo, otherwise please just use the repository.

pedroscaff avatar Jun 06 '20 10:06 pedroscaff

Right on! Usually the -git versions keep up with the actual commits, so I suspect this is up to date? The output of swaywsr --version is 1.0.0 on my system, and yay pulls swaywsr-git 1.0.0.r10.g394c185-1 to build it...

kflak avatar Jun 06 '20 10:06 kflak

thanks for the info, I was not actually keeping track of versions so far :woman_facepalming:, but I will do it from now on, and this bug fix should be the 1.0.1 :). I need to use an older ubuntu version on my work machine so I'm actually using i3 during the day, and sway in my personal laptop but than reduced time hehe. But I will run swaywsr in a terminal and keep an eye on it.

can you please run with cargo run and not with a release version, it is better to detect the bug.

pedroscaff avatar Jun 09 '20 12:06 pedroscaff