15:17 <lillian> hello, what's the easiest way to get a statusbar? i need to run a software whose initial setup is unfortunately through a statusbar menu

15:18 <ifreund> I think you mean a "system tray" to be precise

15:18 <ifreund> Waybar has one iirc, other status bars might as well

15:18 <lillian> yes system tray, sorry

15:19 <lillian> i tried waybar but it's not showing anything

15:19 <ifreund> you proably need to explicitly enable the tray somehow

15:19 <ifreund> https://github.com/Alexays/Waybar/wiki/Module:-Tray

15:22 <LarstiQ> I'm using Waybar for that because I haven't been able to get tray solution with yambar so far (which I otherwise prefer)

15:23 <lillian> oh, turns out i had a broken xdg portal config which did not let waybar start...

15:24 <lillian> LarstiQ, yeah i generally use yambar. there is an open issue for tray

15:46 <adamcstephens> waybar just works :)

18:58 <AlmostSurelyRob> Hello,

18:58 <AlmostSurelyRob> After updating to 3.2 I have been running almost without crashes throughout a busy day, but I still have two random issues. Slack client segfaults when I am on a single monitor (fine when I am on two!) and kanshi doesn't really do hot plugging so I need to restart river completely. Has anyone experienced anything similar?

18:59 <AlmostSurelyRob> With kanshi, I was expecting that after unplugging my two monitors plugged via a docking station, over a USB-C and Thunderbolt in respectively home and office.

18:59 <AlmostSurelyRob> With kanshi, I was expecting that after unplugging my two monitors plugged via a docking station, over a USB-C and Thunderbolt in respectively home and office it will just revert to my builtin monitor on the laptop.

19:16 <AlmostSurelyRob> I don't know if it's related but when I log it I can see:

19:16 <AlmostSurelyRob> [0522/201504.994994:ERROR:elf_dynamic_array_reader.h(64)] tag not found

19:16 <AlmostSurelyRob> just before Slack segfaults.

19:51 <ifreund> AlmostSurelyRob: the kanshi issue kinda sounds like https://todo.sr.ht/~emersion/kanshi/100

19:51 <ifreund> (already fixed upstream, check your kanshi version)

19:52 <ifreund> slack crashing is almost certainly a slack bug, a WAYLAND_DEBUG=1 log of slack running could possibly shed some light

19:56 <AlmostSurelyRob> Thanks! Sorry, I forget that I am on Wayland... This is a known issue and I need to add:

19:56 <AlmostSurelyRob> --enable-features=UseOzonePlatform,WebRTCPipeWireCapturer,WaylandWindowDecorations --ozone-platform=wayland. When I do this, the client correctly boots. I will need to make sure this is in my .desktop file.

19:57 <AlmostSurelyRob> My kanshi is 1.5.1.

20:01 <ifreund> hmm, not that issue then. whats your kanshi config? do you have a profile for only your single builtin laptop monitor?

20:02 <AlmostSurelyRob> profile home {

20:02 <AlmostSurelyRob>     output eDP-1 disable

20:02 <AlmostSurelyRob>     output DP-9 mode 1920x1080 position 0,0

20:02 <AlmostSurelyRob>     output DP-11 mode 1920x1080 position 1920,0

20:02 <AlmostSurelyRob> }

20:02 <AlmostSurelyRob> profile office {

20:02 <AlmostSurelyRob>     output eDP-1 disable

20:02 <AlmostSurelyRob>     output DP-9 mode 1920x1080 position 0,0

20:02 <AlmostSurelyRob>     output DP-10 mode 1920x1080 position 1920,0

20:02 <AlmostSurelyRob> }

20:02 <AlmostSurelyRob> profile unplugged {

20:02 <AlmostSurelyRob>     output eDP-1 mode 3840x2400 scale 2.0

20:02 <AlmostSurelyRob> }

20:02 <AlmostSurelyRob> But I think it does look like the issue that you pointed... I could try adding intermediate profiles, reload and test.

20:03 <AlmostSurelyRob> Unless you're saying that it's been fixed by 1.5.1. The latest release is 1.6.0.

20:04 <AlmostSurelyRob> I wonder if it's important that this is over a docking station so by unplugging one cable, I unplug two monitors.

20:06 <ifreund> A WAYLAND_DEBUG=1 log of kanshi running while you unplug that one cable might be interesting

20:12 <AlmostSurelyRob> Sorry, let me ask if I got it: `riverctl spawn "WAYLAND_DEBUG=1 kanshi > kanshi.log"`?

20:15 <AlmostSurelyRob> Hmm... I tried that, unplugged and plugged again. When I plug back I recover the session, but the log is empty.

20:16 <ifreund> WAYLAND_DEBUG=1kanshi 2> /tmp/out.log

20:16 <ifreund> no need for riverctl spawn, the logging goes to stderr

20:18 <AlmostSurelyRob> I got the log! Thanks, reading...

20:20 <ifreund> you can share it using a pastebin, e.g https://bpa.st

20:21 <AlmostSurelyRob> Hmmm... there's a lot of things going wrong here... For start DP number are changing.

20:21 <AlmostSurelyRob> https://bpa.st/M5TA

20:28 <ifreund> DP-1 is a connector name, so it's not tied to a physical monitor but rather the port on your computer that the monitor is plugged in to, I'm not too surprised that a dock confuses thnigs there

20:28 <ifreund> you probably want to use the monitor's serial or something else more persistant

20:32 <ifreund> AlmostSurelyRob: I think the main issue is you're missing the "enable" in your kanshi config

20:32 <ifreund> e.g. output eDP-1 enable mode 3840x2400 scale 2.0

20:32 <AlmostSurelyRob> Ok. Good idea. So instead of DPs I can just use Serial that is reported in wlr-randr.

20:33 <ifreund> assuming the monitors/docking station expose a useful serial number to the kernel, yes

21:19 <AlmostSurelyRob> That doesn't look like it's the case, serials are identical on both outputs...

21:20 <AlmostSurelyRob> This explains why I would randomly get left/right mixed up when I was using Gnome Shell.

21:24 <AlmostSurelyRob> Hmmm... I suppose my insistence on docking station can be easily resolved though by adding several combinations of DPs. Fortunately, I've got exactly the same setups at home and in the office.