travankor has quit [Remote host closed the connection]
travankor has joined #river
Szadek has joined #river
itshog has joined #river
Guest36 has joined #river
Guest36 has quit [Client Quit]
angry_vincent has quit [Ping timeout: 246 seconds]
Gozenka has joined #river
<Gozenka>
jacobly I've been trying No-XWayland for the past few days. Everything I need seems to work fine.
<Gozenka>
spotify needed some adjustments to enable Wayland-native mode.
<Gozenka>
One peculiar thing in a version with XWayland support; even if I do not start an XWayland-using program, XWayland is still initialized and sometimes user resources.
<Gozenka>
uses*
<ifreund>
Gozenka: yeah, that's done out of simplicity
<Gozenka>
ifreund I tried river and dwl with the Vulkan renderer. It seems to not work properly in river, but it works pretty well in dwl. Is there a reason for that?
<ifreund>
No idea, that's all handled by wlroots. Are you using the same wlroots version?
<Gozenka>
And to my surprise, Chromium got HWAccel for the first time on Wayland for me, out of the box with no flags when I used the Vulkan renderer
angry_vincent has joined #river
angry_vincent has quit [Changing host]
angry_vincent has joined #river
<ifreund>
what doesn't work with the vulkan renderer on river?
<Gozenka>
yep, just with the wlroots 16.2.0 from Arch on both
<ifreund>
my graphics card doesn't have driver support for the extensions required for the vulkan renderer sadly so I can't test
<Gozenka>
constant flickering and weird stuff on Chromium and spotify
<Gozenka>
I don't use any other GUI apps really, so I haven't tested it extensively
<Gozenka>
mpv worked fine
<ifreund>
the only thing I can think of would be that river's approach to frame perfection using saved client buffers might be different from whatever dwl does
<ifreund>
river use the same rough approach as sway there
<ifreund>
like I said though, this is wlroots territory
<Gozenka>
Even wlroots itself still seems to have Vulkan renderer as quite unstable and in testing, so I'm not sure if I will keep using it for now anyway. :)
<ifreund>
yeah, it's not recommend yet
Szadek has quit [Quit: WeeChat 3.8]
Szadek has joined #river
Szadek has quit [Client Quit]
Szadek has joined #river
Gozenka has quit [Quit: Client closed]
Gozenka has joined #river
<Gozenka>
I'd like some suggestions on which bar to use.
<Gozenka>
I only need to see tags and I need colors on the status components.
<Gozenka>
Otherwise I want the most lightweight option.
<Gozenka>
Any recommendations?
omni has quit [Read error: Connection reset by peer]
omni has joined #river
<ifreund>
Gozenka: I think the brand new sandbar fits that description
<Gozenka>
I'll try supplying status text via aslstatus I used in dwm
<Gozenka>
it has an stdout option rather than updating root window name
waleee has joined #river
waleee has quit [Ping timeout: 250 seconds]
waleee has joined #river
Gozenka has quit [Quit: Client closed]
itshog has joined #river
aishathegaul[m] is now known as aisha[m]
itshog has quit [Ping timeout: 250 seconds]
<ifreund>
the new rules system just got pushed to master :)
notzmv has quit [Ping timeout: 264 seconds]
<novakane>
lot of nice improvement in river recently, that's cool
itshog has joined #river
groknull has joined #river
groknull has quit [Remote host closed the connection]
notzmv has joined #river
kotto has joined #river
jao has joined #river
itshog has quit [Ping timeout: 264 seconds]
Szadek has quit [Quit: WeeChat 3.8]
Szadek has joined #river
itshog has joined #river
waleee has quit [Quit: WeeChat 3.8]
upsala has joined #river
Szadek has quit [Ping timeout: 246 seconds]
Szadek has joined #river
<jacobly>
I guess I need a different irc client, any suggestions?
<ifreund>
jacobly: I use weechat personally, it's a love/hate thing though
<hryx>
jacobly: I've been using weechat running on a home server and connecting to it with tmux, I like it
Gozenka has joined #river
<hryx>
heh
<ifreund>
what's wrong with your current client?
<jacobly>
it depends on gtk 2
<novakane>
senpai is nice for something really simple
<Gozenka>
ifreund river with Vulkan renderer works fine today.
<Gozenka>
sorry, it seems I probably had something set up differently when trying it yesterday, although I had cleaned up wlroots and everything and reinstalled.
<ifreund>
no worries, glad it's not some freaky bug :)
itshog has quit [Ping timeout: 250 seconds]
Gozenka has quit [Quit: Client closed]
Gozenka has joined #river
<Gozenka>
Would the new ssd rule prevent the title bar from appearing? I get an annoying title bar on Zathura in river.
<ifreund>
Gozenka: no, for that one would need to patch gtk or implement a kde-specific that's been obsolete for like 5 years
<ifreund>
*kde-specific protocol
Gozenka has quit [Ping timeout: 260 seconds]
<ifreund>
there is a behavior change on master related to this, river will no longer draw SSD borders on clients that don't support the xdg-decoration protocol by default
<ifreund>
the old behavior can be stored with `riverctl rule-add ssd` which overrides the default of honoring the client's preference and forces ssd on everything
hryx has quit [*.net *.split]
emersion has quit [*.net *.split]
emersion_ has joined #river
hryx has joined #river
emersion_ is now known as emersion
angry_vincent has quit [Remote host closed the connection]
<Gozenka>
This in .config/gtk-3.0/gtk.css solves it without needing to patch gtk
<Gozenka>
might mention it on faq if other people are not happy with this
Gozenka has quit [Quit: Client closed]
<ifreund>
(added that css snipped and my 1 line gtk patch to the wiki)
<jacobly>
somehow made it
<jacobly>
I just needed -Dxwayland to use my old irc client
<jacobly>
now if only I could remember how to setup notifications
<ifreund>
ah, I probably should have mentioned that. I thought you just want to be a wayland purist and avoid X11 clients :D
<jacobly>
I was avoiding X11 because it kept crashing
<jacobly>
I'm used to that meaning that mesa was miscompiled, but in this case it was just that Xwayland wasn't running
<ifreund>
yeah, -Dxwayland is kind like zig's -Denable-llvm currently
<ifreund>
almost everyone wants to be using it but we have hopes that someday things might be different
<plumeus>
huh, I've actually been doing mostly fine without XWayland for the longest time
<plumeus>
I enabled it to play some video game... ugh
<plumeus>
Wayland support for WINE should make things nicer. Although the game I was playing was native.
<jacobly>
hmm, notifications are working for browser but not irc
<ifreund>
jacobly: what notification daemon are you using? Might be some dbus issue
<jacobly>
it's definitely a dbus issue: Failed loading notification plugin: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
<jacobly>
is there a notification daemon that is more likely to work?
<ifreund>
I think that means that you don't have a notification daemon implementing that interface running
<ifreund>
mako works pretty well on river
<jacobly>
yeah I'm using mako
<ifreund>
might need to start river with `dbus-run-session river` or somethign
<ifreund>
I've never really spent the time to understand dbus on a deep level but I do that and things seem to work
<jacobly>
jacob 676 0.0 0.0 8956 4608 ? Ss 17:53 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-on
<jacobly>
I think that's fine
<kotto>
Hi, I'm trying to use zig-wayland to get the tags from the river protocol, but if I try to `scanner.generate("zriver_output_status_v1", 1);` the scanner says there is no interface `zriver_output_status_v1`
<ifreund>
kotto: generate only accepts global interfaces, you probably want scanner.generate("zriver_status_manager_v1", 4);
<ifreund>
(it should give a better error message though...)
<ifreund>
actually it does say global, "error(zig-wayland): requested global interface 'zriver_output_status_v1' not found in provided protocol xml"
upsala has quit [Remote host closed the connection]
<kotto>
ok, how do I know which is the global interface? And in this case I can access the `zriver_output_status_v1` through the `...manager`?
<kotto>
This is my first time trying to use wayland and that protocol stuff is still quite confusing for me.
<ifreund>
kotto: a global interface is one that is advertised by the compositor over the wl_registry
<ifreund>
you bind the global using the wl_registry.bind request which will create a river status manager object
<ifreund>
then you can use the get_output_status request on that object to create an output status object
<ifreund>
running e.g. wayland-info will print out all the global interfaces advertised by the compositor
<jacobly>
I installed libnotify and its utility outputs the same error lol
<ifreund>
jacobly: are you 100% sure mako is running?
<ifreund>
that's the exact error I get if mako isn't running
<jacobly>
ok that helps
<jacobly>
ok so the auto launch thing wasn't working because dbus wasn't running under wayland
Gozenka has joined #river
<Gozenka>
river crashes when there is no output enabled even for a moment. is that normal?
<Gozenka>
i.e. I have this keymap to switch from my laptop screen to external monitor, and it crashes. if I do the commands separately with time in between, it is fine.
<Gozenka>
riverctl map normal Super P spawn "wlr-randr --output HDMI-A-1 --on --mode 1920x1080; wlr-randr --output eDP-1 --off"
<Gozenka>
or if I hit my apparently crappy HDMI cable, momentarily disrupting the output to the external monitor, river crashes
<Gozenka>
I'm on Vulkan at the moment, in case it is relevant
<Gozenka>
if this is normal behavior, I think it would be much better to handle "no output" somehow, if it is doable.
hryx has quit [Quit: WeeChat 2.8]
hryx has joined #river
<ifreund>
Gozenka: definitely not normal, Ill have a look in the morning
<Gozenka>
I'll see if it happens on GLES too
Gozenka has quit [Quit: Client closed]
Gozenka has joined #river
<Gozenka>
Yep, happens on GLES too.
<Gozenka>
Also, adding sleep 1 between the commands did not work neither.
<Gozenka>
I mean, that would just be a workaround for my use-case, and a longer delay would work.
<Gozenka>
Also, I know Vulkan is not a priority and this is not related to river I think, but one small bug report:
<Gozenka>
In terminal, sometimes black lines occur, e.g. when writing stuff on neovim. I guess it is elated to damage tracking.
<Gozenka>
emersion
<Gozenka>
I believe I did not experience this when I used dwl with the git version of wlroots.
Gozenka has quit [Quit: Client closed]
Gozenka has joined #river
<Gozenka>
OK, other bug, might be related.
<Gozenka>
- Start river with eDP enabled, HDMI disabled.
<Gozenka>
- Enable HDMI (not disabling eDP)
<Gozenka>
- Both monitors seem to be active.
<Gozenka>
- Cannot do anything, cannot spawn windows. Switching to other monitor and trying to spawn a window crashes river.
<Gozenka>
Should I try to get some logs and open an issue?
<Gozenka>
This does not happen if I start river with both monitors active