Home liberachat/#xmonad: Logs Calendar

Logs: liberachat/#xmonad

←Prev  Next→ 184,942 events total
2023-05-06 23:07:07 × joshproehl quits (~quassel@user/joshproehl) (*.net *.split)
2023-05-06 23:07:07 × justache quits (~justache@user/justache) (*.net *.split)
2023-05-06 23:07:07 × dminuoso quits (~dminuoso@user/dminuoso) (*.net *.split)
2023-05-06 23:07:19 hrberg joins (~quassel@171.79-160-161.customer.lyse.net)
2023-05-06 23:07:19 piele joins (~piele@tbonesteak.creativeserver.net)
2023-05-06 23:07:49 laman2 joins (~laman@rego.ai)
2023-05-06 23:07:55 joshproehl joins (~quassel@user/joshproehl)
2023-05-06 23:09:03 justache joins (~justache@user/justache)
2023-05-06 23:09:03 × justache quits (~justache@user/justache) (Max SendQ exceeded)
2023-05-06 23:09:04 dminuoso joins (~dminuoso@user/dminuoso)
2023-05-06 23:11:19 yosafbridge joins (~yosafbrid@static.38.6.217.95.clients.your-server.de)
2023-05-06 23:13:28 justache joins (~justache@user/justache)
2023-05-07 00:23:07 × tremon quits (~tremon@83.80.159.219) (Quit: getting boxed in)
2023-05-07 00:30:14 <geekosaur> albatross, why were you trying to restart it?
2023-05-07 00:30:44 <geekosaur> if you make chyanges to your config and you want them to take effect, you press (by default) mod-q.
2023-05-07 00:31:10 <albatross> I wasn't in X to do that
2023-05-07 00:31:33 <geekosaur> `xmonad --restart` is only half of that, and it restarts the existing configuration without rebuilding it. you need `xmonad --recompile` to do that part
2023-05-07 00:32:07 <albatross> neither command worked, gave an error message like "user error (openDisplay)"
2023-05-07 00:32:18 <geekosaur> also `xmonad --recompile` and `xmonad --restart` need to be run within X because thjey send X messages
2023-05-07 00:32:40 <albatross> X was still running, I just wasn't in X
2023-05-07 00:32:41 <geekosaur> well, recompile should work but restart won't be able to connect to the X server
2023-05-07 00:33:01 <albatross> like I could use vtty
2023-05-07 00:33:07 <geekosaur> but because you weren't in X, restart couldn't connect to it
2023-05-07 00:35:17 <albatross> surely those commands have no one to distinguish being run from a vtty or an xterminal? so long as there is an x server running they would work, I would think
2023-05-07 00:35:29 <geekosaur> and even if it somehow managed to authorize with the X server from outside, it still wouldn't have done anything noticeable unless you had changed your config and rebuilt it with `xmonad --recompile`
2023-05-07 00:36:40 <geekosaur> X used to work that way. it meant anyone who could get into your syste,m from a network connection could do things like sniff passwords. X is insecure enough as it is
2023-05-07 00:36:42 <albatross> or does xterm set up some env variables with information about the x server that is missing from a virtual console
2023-05-07 00:37:22 <albatross> hmmm so is there some way for me to cleanly restart xmonad from command line then?
2023-05-07 00:37:33 <albatross> if I'm stuck in a virtual console
2023-05-07 00:38:25 <albatross> or somehow get back to X. It is academic at this point anyhow
2023-05-07 00:39:27 <geekosaur> you need to find out where the Xauth tickets are stored and point to them with the XAUTHORITY environment variable. sometimes it's stored in ~/.Xauthority and things will work fairly easily, but sometimes they're hidden away by the display manager
2023-05-07 00:40:12 <albatross> I see. That doesn't sound any more secure haha. Good to know for next time I guess...
2023-05-07 00:40:55 <geekosaur> the default isn't, but display managers as I said can hide them away better
2023-05-07 00:41:11 <geekosaur> I'm not sure why more of them don't
2023-05-07 00:41:52 <geekosaur> it was a much simpler world in 1986 when this stuff was designed
2023-05-07 00:42:16 <albatross> I feel like if someone other than me can log in to my system I have bigger issues, really.
2023-05-07 00:42:56 <geekosaur> you mostly do, yes. but this doesn't require full log in to exploit, sadly
2023-05-07 00:43:55 <albatross> ok well I won't pretend to understand the majesties of X internals haha
2023-05-07 00:44:41 <immibis> albatross: is the $DISPLAY environment variable set?
2023-05-07 00:44:53 <immibis> on most/all distributions, just set: export DISPLAY=:0
2023-05-07 00:45:05 <immibis> and then your X-related commands know which X server to connect to
2023-05-07 00:45:16 <albatross> I can't go back in time to check but I'll keep that in mind for future
2023-05-07 00:45:23 <immibis> that's for your typical case. on weird or multi-user systems it might not be :0
2023-05-07 00:45:54 <immibis> xauth is usually stored in a place that's accessible to any process in your user account, so it's not an issue, but there is also a way to transfer it to other user accounts if you need that
2023-05-07 00:46:16 <immibis> but DISPLAY is (more-or-less) specific to the terminal
2023-05-07 00:59:40 <geekosaur> it does go a little beyond that; AIUI Fedora uses cgroups to limit access to the session
2023-05-07 01:00:06 <geekosaur> (Debian/Ubuntu/Mint use an older version of cgroups and systemd isn't configured to make use of it anyway)
2023-05-07 01:00:41 <geekosaur> liskin knows more about this, I believe he's got his system set up to use systemd for session control
2023-05-07 02:24:08 × td_ quits (~td@i5387090E.versanet.de) (Ping timeout: 240 seconds)
2023-05-07 02:26:07 td_ joins (~td@i53870927.versanet.de)
2023-05-07 03:17:34 rekahsoft joins (~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca)
2023-05-07 03:54:21 × rekahsoft quits (~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca) (Ping timeout: 256 seconds)
2023-05-07 05:25:08 × werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 240 seconds)
2023-05-07 05:25:23 werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-05-07 06:19:25 × werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 240 seconds)
2023-05-07 06:21:31 werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-05-07 06:35:54 thyriaen joins (~thyriaen@91.197.68.193)
2023-05-07 07:19:29 × thyriaen quits (~thyriaen@91.197.68.193) (Ping timeout: 256 seconds)
2023-05-07 07:34:21 chomwitt joins (~chomwitt@2a02:587:7a1f:b500:1ac0:4dff:fedb:a3f1)
2023-05-07 08:04:18 th3m45t3rm1nd joins (~th3m45t3r@2401:4900:4048:9364:ac35:cb57:fe94:51d0)
2023-05-07 08:18:28 thyriaen joins (~thyriaen@91.197.68.193)
2023-05-07 08:25:42 × thunderrd quits (~thunderrd@183.182.115.197) (Remote host closed the connection)
2023-05-07 09:00:11 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-05-07 09:00:11 × unclechu quits (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-05-07 09:29:57 × th3m45t3rm1nd quits (~th3m45t3r@2401:4900:4048:9364:ac35:cb57:fe94:51d0) (Quit: Client closed)
2023-05-07 11:01:31 <liskin> Debian definitely uses cgroupsv2 these days
2023-05-07 11:01:39 <liskin> And so does its systemd build
2023-05-07 11:01:43 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
2023-05-07 11:01:57 unclechu joins (~unclechu@2001:470:69fc:105::354)
2023-05-07 11:37:52 th3m45t3rm1nd joins (~th3m45t3r@2401:4900:4048:9364:ac35:cb57:fe94:51d0)
2023-05-07 12:25:07 × th3m45t3rm1nd quits (~th3m45t3r@2401:4900:4048:9364:ac35:cb57:fe94:51d0) (Quit: Client closed)
2023-05-07 12:51:59 × chomwitt quits (~chomwitt@2a02:587:7a1f:b500:1ac0:4dff:fedb:a3f1) (Remote host closed the connection)
2023-05-07 14:54:56 tremon joins (~tremon@83.80.159.219)
2023-05-07 16:00:07 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-05-07 16:00:07 × unclechu quits (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-05-07 17:00:36 mc47 joins (~mc47@xmonad/TheMC47)
2023-05-07 17:10:23 werneta_ joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-05-07 17:14:56 × tremon quits (~tremon@83.80.159.219) (*.net *.split)
2023-05-07 17:14:56 × werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (*.net *.split)
2023-05-07 17:23:30 tremon joins (~tremon@83.80.159.219)
2023-05-07 18:19:00 Maeda joins (~Maeda@91-161-10-149.subs.proxad.net)
2023-05-07 18:39:11 × Natch quits (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) (Read error: Connection reset by peer)
2023-05-07 18:43:08 Natch joins (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se)
2023-05-07 20:14:38 × thyriaen quits (~thyriaen@91.197.68.193) (Quit: Leaving)
2023-05-07 21:39:13 × mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-05-07 23:32:25 × tremon quits (~tremon@83.80.159.219) (Quit: getting boxed in)
2023-05-08 02:23:45 × td_ quits (~td@i53870927.versanet.de) (Ping timeout: 240 seconds)
2023-05-08 02:25:54 td_ joins (~td@i53870906.versanet.de)
2023-05-08 05:33:00 × werneta_ quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 250 seconds)
2023-05-08 05:33:50 werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-05-08 05:37:25 <Solid[m]> geekosaur yeah sorry I've been super swamped with work lately (preparing conference talks for this summer…)
2023-05-08 05:37:40 <Solid[m]> (and as liskin correctly said I couldn't have approve the expense anyways)
2023-05-08 06:43:40 th3m45t3rm1nd joins (~th3m45t3r@169.150.196.92)
2023-05-08 07:09:24 × th3m45t3rm1nd quits (~th3m45t3r@169.150.196.92) (Quit: Client closed)
2023-05-08 07:10:40 <geekosaur> you can now. (I think having the only two people able to approve them being the two most likely to be offline is not so hot)
2023-05-08 07:10:53 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
2023-05-08 07:11:07 unclechu joins (~unclechu@2001:470:69fc:105::354)
2023-05-08 07:23:18 <geekosaur[m]> hm, bridge is being very slow again. anyway, you are now 😄 (bad news if the only two in a position to approve are the ones most likely to be offline)
2023-05-08 07:47:36 th3m45t3rm1nd joins (~th3m45t3r@169.150.196.92)
2023-05-08 07:54:24 × Maeda quits (~Maeda@91-161-10-149.subs.proxad.net) (Quit: leaving)

All times are in UTC.