pixavi has quit [Remote host closed the connection]
AssWorm has joined #river
AssWorm2 has joined #river
AssWorm2 has quit [Client Quit]
<AssWorm>
I hope this week the river 0.4.0 will be released or at least in this month
AssWorm has quit [Quit: Client closed]
<ifreund>
yeah, not gonna happen
flower_ has joined #river
aelius has joined #river
sugarbeet has quit [Ping timeout: 244 seconds]
sugarbeet has joined #river
dmcblue has joined #river
<dmcblue>
Nickli Thanks for showing me that package! Finally got it working, just had to run `cycle-focused-tags` with sudo one time to get it to generate the river bindings correctly (in case anyone else has trouble with it)
<Nickli>
👍
<dmcblue>
This might be more of a Wayland question than a River one, but what is the way / a good way to have the screen shut off after inactivity (or with a hotkey)? Not necessarily have the computer sleep but at least to shut down the signal to the monitor. My google searching is not coming up with much, probably using the wrong search terms. Even if
<dmcblue>
someone can just point me in the right direction, that'd be great
<FireFly>
oh that might be nicer than my hacky shellscript around xbacklight
<szgy>
I y'all. Did anyone using an arch based distro had any issues after recent updates? I had to freeze the system updates from like, 15th of march because I started having a full freeze of graphics.
<szgy>
I wasn't able to pinpoint it to any app (like firefox, a webkit based browser, slack, nor anything). Also river logs don't show anything weird.
<szgy>
It only graphical since audio still works; and its not a kernel panic
<szgy>
(I know this is a river channel only, but maybe someone had a similar experience). I'm guessing wayland logs should appear on the river logs itself and there's no other place to look for those
<szgy>
but maybe I'm mistaken...
<ifreund>
szgy: anything in dmesg?
<ifreund>
also amd or intel gpu?
<ifreund>
support in amdgpu for older amd hardware often has regressions
<szgy>
amd! but is a pretty new thinkpad
<szgy>
I'm not clear how to see dmesgs from older boots (or do they accumulate?)
<szgy>
but at a glance I couldn't see anything weird there...
<ifreund>
I think saving dmesg logs from previous boots depends on your distro, I assume systemd journald does something about that though
<leon-p>
yes, you can look at journald entries from previous boots
<leon-p>
I think it was journalctl --boot -1
<leon-p>
or hit tab after "journalctl --boot" to see the ids of all stored boots and use one of those
cer-0 has quit [Remote host closed the connection]
cer-0 has joined #river
kansei has quit [Ping timeout: 244 seconds]
<szgy>
leon-p: (don't have systemd - I'm actually using artix) but dinit and there's nothing on its logs useful)
<ifreund>
if you're using artix you're probably on your own as far as robust logging goes
<ifreund>
I'd definitely set something up so you can check dmesg output after hitting that freeze issue
<szgy>
yep, I figured...
<leon-p>
is it just me or are most anti systemd distros completely half-assed out of the box? keeping logs from previous boots is a pretty basic thing, no?
<szgy>
heh yeah. I mean, I never had any issues with artix (been using it for like, 5 years) and I actually forget that I'm using artix instead of arch most of the time
<szgy>
so yeah, I never had any need for inspecting system logs before
<szgy>
but for this specific thing is kind of a drag...
cer-0 has quit [Remote host closed the connection]
waleee has joined #river
Nickli has quit [Ping timeout: 268 seconds]
pixavi has joined #river
pixavi has quit [Quit: pixavi]
pixavi has joined #river
pixavi has quit [Client Quit]
pixavi has joined #river
cer-0 has joined #river
pixavi has quit [Remote host closed the connection]
aelius has quit [Remote host closed the connection]
aelius has joined #river
<ifreund>
leon-p: it's not just you, chimera is the only one that seems to be making an effort to match the actually really useful features of systemd
<ifreund>
artix supports like 5 different init systems, which means that no init system is really well integrated
<ifreund>
though I also wouldn't call chimera an "anti-systemd" distro, it uses ports of several parts of systemd
<leon-p>
it probably isn't an "anti-systemd" distro. I just find most distros using other inits smell more like a knee-jerk reaction than a proper effort so that's why the term came to mind
flower_ has quit [Quit: Lost terminal]
elagost has quit [Quit: WeeChat 4.4.4]
elagost has joined #river
elagost has quit [Client Quit]
<ifreund>
oh, there are absolutely plenty of "anti-systemd" knee-jerk people out there :D
elagost has joined #river
aelius has quit [Remote host closed the connection]
<bwbuhse>
ifreund: I (personally) think Gentoo is pretty good at at least presenting alternatives to systemd tools
aelius has joined #river
elshize has quit [Ping timeout: 260 seconds]
sewn has quit [Remote host closed the connection]
sewn has joined #river
<bwbuhse>
as in, I honestly am not sure if there's anything I've had issues with or that Ifeel are particularly annoying with systemd. Gentoo has first-class support for systemd, too, anyways