00:03 <cruxbot> [opt.git/3.6]: thunderbird-bin: updated to version 102.0.3

00:03 <cruxbot> [opt.git/3.6]: irssi: updated to version 1.4.2

00:05 <cruxbot> [contrib.git/3.6]: docker-compose: updated to version 2.7.0

00:05 <cruxbot> [contrib.git/3.6]: kodi: updated patch for fmt 9.x

01:26 <waylandtesterwmf> wow, 42 people without sleeping

01:26 <waylandtesterwmf> good morning

01:27 <waylandtesterwmf> where I can download iso 3.7 for testing?

01:27 <waylandtesterwmf> and I read https://crux.nu/Main/ReleaseNotes3-7

01:28 <waylandtesterwmf> I want Wayland native desktop. How install CRUX without X (with gtk for browser)?

01:28 <waylandtesterwmf> I prefer WM (DWL), depends - wlroots and wayland-protocol. That's all.

01:29 <waylandtesterwmf> And who say about date of release 3.7 ver?

01:30 <waylandtesterwmf> bye, I read all answers on libera log. Cheers

01:58 <jaeger> You can install wayland stuff in 3.6 but you can find the test ISO at https://crux.ninja/tmp/ as well - it's NOT ready yet, keep in mind. No release date yet but we're working on it.

02:40 <cruxbot> [contrib.git/3.6]: clamav: updated to version 0.105.1

03:46 <waylandtesterwmf> jaeger: thanks for fast answer.

04:32 <brian|lfs> I keep getting /usr/bin/python3: No module named build

04:33 <brian|lfs> on crux 3.7 not sure what needs to be installed or rebuilt I rebuilt python3

05:18 <braewoods> build module isn't present.

05:18 <braewoods> https://pypi.org/project/build/

11:44 <cruxbot> [opt.git/3.6]: [notify] samba: security update to 4.16.4

11:44 <cruxbot> [opt.git/3.6]: tevent: update to 0.13.0

11:44 <cruxbot> [opt.git/3.6]: ldb: update to 2.5.2

15:45 <deep42thought> Hi romster, I can't upgrade p5-uri, because the source is unavailable - there's 5.10 and 5.12 but no 5.11 :-(

15:46 <stenur> was reported already a week ago or so

15:46 <stenur> but by me ... so maybe we now have more luck

15:51 <deep42thought> I wouldn't expect a fix in the next few hours - it's early in the morning in romster's local time ;)

15:52 <deep42thought> stenur: did you open a bug in flyspray already?

15:56 <stenur> no that not

15:56 <deep42thought> will do

15:57 <braewoods> Romster isn't even here.

15:58 <deep42thought> yeah, but he could read the logs ;)

15:58 <deep42thought> anyway, I opened a bug, so he will get notified :)

15:58 <braewoods> He's probably retired to enjoy life on that virtual farm by now.

15:59 <deep42thought> enjoy *what*?

15:59 <braewoods> Well I've been observing his behavior for months now. He's been mostly dormant here and been doing some kind of farming simulator gaming instead as far as I can tell.

16:00 <deep42thought> speaking of "life", I have to get back to mine, too ;) cya later!

16:30 <SiFuh> braewoods: Romster is still here he is just pre-occupied and he notified all of us long ago

16:37 <SiFuh> He doesn't have to be here, he just chooses to be. Sorry if I sound a bit harsh, but I don't mean to sound that way.

18:37 <dlcusa> As for all contributors to CRUX, I am thankful for everything Romster has done and will be grateful for anything else done in the future with no expectations of such activity. Contributors are owed, not owing. If they have a sense of duty to contribute, that's great, and maybe even appropriate, but not expected. Speaking for myself.

20:15 <elderK> Hey guys, I have a bunch of questions for you :) The first question is how you ensure a dbus session is started for your user when you log in. From googling, it seems a lot of people will just start a session in their .bash_profile via dbus-run-session or in their .xinitrc via dbus-launch.

20:16 <elderK> My issue with the first solution is that if you have multiple login sessions, the dbus session will not be shared. So, I will need to roll my own method to keep track of how many login sessions there are and kill the dbus daemon when the last "login" is logged out.

20:17 <elderK> Issue with the X11 approach is that stuff that requires dbus will not function until I enter X11. If I'm using pipewire or whatever, I need that dbus daemon to be running so that pipewire, pipewire-pulse and wireplumber all talk.

20:17 <elderK> I was wondering how you guys solved this. So far, my idea is to to use dbus-run-session in the login script if and only if some state isn't available. If it's not available, I run via dbus-run-session and then dump that state. The state also contains a reference count so I know when to kill dbus in .bash_logout.

20:18 <elderK> Regarding X11, I'm also curious about display managers but I haven't thought of a good way to handle multiple monitors that are dynamically placed. I use autorandr to manage my displays when I'm in X11: I have a laptop and it may be connected to none, one or two external displays.

22:04 <jaeger> I'm no expert on dbus stuff, I've just run a dbus-run-session or dbus-launch from .xinitrc or similar

22:17 <elderK> What about multiple login sessions sharing the same bus?

22:20 <jaeger> Not something I've ever had to think about, I guess

22:21 <jaeger> Works fine for multiple tasks in a single X or wayland session