aryak has quit [Remote host closed the connection]
aryak has joined #river
jao has quit [Ping timeout: 255 seconds]
angry_vincent has joined #river
angry_vincent has quit [Changing host]
angry_vincent has joined #river
ayushnix has quit [Changing host]
ayushnix has joined #river
ayushnix has quit [Ping timeout: 260 seconds]
repoman has joined #river
Guest89 has joined #river
Guest89 has quit [Client Quit]
hewxle has joined #river
notzmv has quit [Ping timeout: 265 seconds]
waleee has quit [Quit: WeeChat 3.8]
Ordoviz has joined #river
RZ_MJ[m] has joined #river
Ordoviz has quit [Ping timeout: 246 seconds]
Ordoviz has joined #river
Ordoviz has quit [Ping timeout: 248 seconds]
Ordoviz has joined #river
hewxle has quit [Remote host closed the connection]
Ordoviz has quit [Ping timeout: 265 seconds]
waleee has joined #river
leopoldek has quit [Ping timeout: 250 seconds]
waleee has quit [Ping timeout: 240 seconds]
waleee has joined #river
waleee has quit [Quit: WeeChat 3.8]
Ordoviz has joined #river
<ccha>
hello, is it normal that ps display the init as defunct?
<ifreund>
ccha: yeah, if your init exits before river does it will hang around as a zombie currently
<ifreund>
if the init process is still around when river exits it will send SIGTERM to the init process groug
<ifreund>
it's not ideal to leave the zombie around I guess but I'm not sure it's an issue in practice
waleee has joined #river
waleee has quit [Ping timeout: 246 seconds]
Ordoviz has quit [Ping timeout: 252 seconds]
Ordoviz has joined #river
jao has joined #river
Ordoviz has quit [Ping timeout: 252 seconds]
Ordoviz has joined #river
Nulo has quit [Read error: Connection reset by peer]
Nulo has joined #river
Ordoviz has quit [Quit: WeeChat 3.8]
hochata has joined #river
Ordoviz has joined #river
<kraem_>
ok so i still have some problems with my external monitor. i tried running without kanshi for a bit but the same thing is happening so i'm guessing the problem is within river. 1. plug in external monitor (both my internal and external monitor are active and can be used normally) 2. open wdisplays and disable my internal monitor. now the internal monitor powers down as it should and the external monitor is powered on although my windows seems
<kraem_>
stuck on the powered down internal monitor. i can't focus the external monitor with mod + . nor move the open windows to the external monitor with mod + shift + .. river hasn't froze since i can see the wdisplays overlay flickering (as it always does) indicating which monitor is which on the external display .
<kraem_>
hi btw :)
<kraem_>
and i'm on master b369815
leopoldek has joined #river
<ifreund>
kraem_: I'm aware of an issue related to that on master unfortunately, it looks like there's nothing to track it on the github issue tracker yet though unfortunately
Ordoviz has quit [Quit: WeeChat 3.8]
Szadek has quit [Ping timeout: 250 seconds]
alexherbo2 has joined #river
angry_vincent has quit [Remote host closed the connection]
Guest99 has joined #river
Guest99 has quit [Client Quit]
Szadek has joined #river
waleee has joined #river
hochata has quit [Remote host closed the connection]
alexherbo2 has quit [Ping timeout: 260 seconds]
alexherbo2 has joined #river
Guest99 has joined #river
Guest99 has quit [Ping timeout: 260 seconds]
alexherbo2 has quit [Remote host closed the connection]
<NickH>
ifreund and kraem_ I see this too. I didn't post a github issue yet since I don't have time to loose my session trying to understand it right now.
<NickH>
If I can find time what sort of debug info would be useful? Just run with "river -log-level > river.log 2>&1"?