[arch-general] i3wm (randomly?) freezes; SIGCONT seems to fix it

[Bennett Piater]

> (I think I managed to trace them back to Sept 1st and Sept 5th).

My last update before the apparently breaking one was 2016-08-24.
So, maybe some upgrade between 2016-08-24 and 2016-09-04 doesn't play
well with i3...

Would you mind cross-checking your upgrades between 2016-08-24 and
2016-09-01 with my log [0] when you have the time?

> After a quick look at my journalctl, I can't really see anything suspicious.

i3wm doesn't log to systemd. I produce my logs by starting i3 with

    exec i3 --shmlog-size=26214400 -V -d all > ~/.i3/logs/$(date
-Iseconds).log

in my ~/.xinitrc.

However, they don't produce any useful information AFAICT, even with
debug verbosity.

Is it possible that i3 receives SIGSTOP for some reason?

Merci beaucoup,
Bennett

[0]: https://vps1.piater.name/commie/#dvm1K6lg

-- 
GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20160909/2fae2d4d/attachment.asc>