2024-12-03.log

- mjw (QUIT: Ping timeout: 245 seconds) (~mjw@gnu.wildebeest.org)00:54
- mtm (QUIT: Ping timeout: 252 seconds) (~textual@47.202.75.129)01:03
+ mtm (~textual@47.202.75.129)01:06
- aloo_shu (QUIT: Ping timeout: 272 seconds) (~aloo_shu@85.51.17.211)02:44
+ aloo_shu (~aloo_shu@90.166.98.125)02:47
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)03:03
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)03:03
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)03:04
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)03:04
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)03:06
+ jacobk (~quassel@2603:8080:b200:7b02::b71)03:07
- jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@2603:8080:b200:7b02::b71)03:21
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)03:40
- GNUmoon (QUIT: Ping timeout: 260 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)03:49
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)03:50
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)03:52
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)03:52
- cobra (QUIT: Quit: ZNC 1.8.2 - https://znc.in) (~cobra@user/Cobra)03:57
- paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@107.159.243.8)04:10
+ cobra (~cobra@user/Cobra)04:12
- josch (QUIT: Ping timeout: 248 seconds) (~josch@mister-muffin.de)05:01
+ josch (~josch@mister-muffin.de)05:23
- GNUmoon (QUIT: Ping timeout: 260 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)07:05
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)07:16
Manis3.0 motherboard ≠ next, right?09:34
- jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:04
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:05
minuteManis: correct, these are two different laptops10:08
+ mjw (~mjw@gnu.wildebeest.org)10:38
joschhuh... i just learned that i can have sway open multiple times on multiple ttys10:54
joschis this something other people do as well? any pitfalls in such a setup?10:55
minuteoh never tried11:21
gsorahmm sounds like a multi-seat setup11:32
- mjw (QUIT: Ping timeout: 260 seconds) (~mjw@gnu.wildebeest.org)12:24
+ chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1)12:25
* Guest1637 -> mjw12:33
+ paperManu (~paperManu@107.159.243.8)12:37
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.98.125)12:40
+ aloo_shu (~aloo_shu@90.166.98.125)12:50
- chomwitt (QUIT: Ping timeout: 265 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1)13:01
+ gustav28 (~gustav@78.82.53.73)13:02
- mtm (QUIT: Ping timeout: 252 seconds) (~textual@47.202.75.129)13:03
+ mtm (~textual@47.202.75.129)13:05
- iank (QUIT: Quit: ZNC 1.8.2+deb2+deb11u1 - https://znc.in) (~iank@fsf/staff/iank)13:25
+ iank (~iank@fsf/staff/iank)13:26
- aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@90.166.98.125)13:43
+ aloo_shu (~aloo_shu@90.166.98.135)13:50
+ chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1)13:56
- chomwitt (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1)14:12
mhoyejosch: no pitfalls afaik. I do the same thing with cage.14:14
mhoyecage -s lets you switch in and out of the vts, it's good.14:18
+ aloo_shu_ (~aloo_shu@90.166.193.71)14:36
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.98.135)14:36
* aloo_shu_ -> aloo_shu14:36
joschnope, it's a bad idea...14:56
joschi cannot sign any gpg messages anymore because the gpg-agent.service errors out14:56
joschwith failed to unprotect the secret key: Inappropriate ioctl for device14:56
joschlogging in a second time and running sway must've messed up something there...14:57
minutehow are those sessions exactly managed/kept separate is the question14:57
joschindeed... :/14:57
minutebut surely gpg-agent should work somehow for multiple sessions in parallel, i.e. desktop + ssh14:58
minutei feel like i should read a book about systemd if it exists14:58
minuteand seatd...14:58
joschrunning my command with GPG_TTY=$(tty) set fixes the problem15:03
joschso somehow the tty connection got lost...?15:03
+ bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com)15:08
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com)15:46
+ bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com)15:46
hramrachthere is a blog about systemd. It goes to great detail about many topics but could not find any information on the core functionality of systemd: how systems using systemd boot.16:13
+ FaRiD (~bizimmeka@213.172.85.35)16:13
hramrachas for gpg-agen if you had two sessions for two users that would likely not be a problem, the problem is likely that the socket gets broken when second gpg-agent is started.16:14
- FaRiD (PART: !!unknown attribute: msg!!) (~bizimmeka@213.172.85.35)16:17
hramrachFor ssh-agent I crafted a baroque script that looks for a seved socket location, and the socket is live, and if so it uses that, and if not it starts a new agent (not session managed), and saves the socket location. The problem with session-managed agent is that it stops when the WM crashes. The problem with .profile is that Wayland (unlike X11) likely no longer runs shell as part of session16:19
hramrachsetup.16:19
joschhramrach: yes, the socket is probably in /run/user/1000/gnupg/ but even after stopping all gpg processes and cleaning that directory, the issue is not fixed for some reason16:19
joschso i wonder where else state related to this is being kept...16:20
+ MyNetAz (~MyNetAz@user/MyNetAz)16:26
ch~/.gnupg/S.gpg-agent?16:27
chalso, is it even gpg-agent for you?16:27
chand not the gnome keyring agent...16:27
chi looked at this the other day and was very confused about how all of this should work16:28
sigridfor me (on either alpine or nixos) adding a bit to the bash profile helped before:16:31
sigridgpg-connect-agent updatestartuptty /bye &>/dev/null16:31
sigridexport SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket)16:31
sigridnot like the second line is needed unless you're using gpg for your ssh keys16:32
chyeah, thats the common workaround, that seemed like it would work, but also wrong16:32
sigridwrong in what sense?16:33
chimo these things should be set in the entire sway session, and not in each "xterm" 16:40
chbecause then gui programs launched from sway dont see them16:40
+ chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1)16:47
joschoh dear...16:50
joschit was gnome-keyring-daemon16:50
joschkilling it fixed the issue...16:50
joschchomwitt: thank you!16:51
joscherrr16:51
joschch: thank you!16:51
chyw16:51
chyeah so idk why gpg-agent.service exists at all16:52
- chomwitt (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1)16:52
+ midfavila (midfavila@sdf.org)17:20
+ glu__ (~glu@user/glu)17:32
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com)17:32
- glu (QUIT: Ping timeout: 265 seconds) (~glu@user/glu)17:33
* glu__ -> glu17:33
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)18:01
+ colinsane (~colinunin@97-113-142-105.tukw.qwest.net)18:14
+ mark_ (~mjw@gnu.wildebeest.org)18:26
+ bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com)18:39
* mjw -> Guest861918:57
- Guest8619 (QUIT: Killed (iridium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)18:57
* mark_ -> mjw18:57
+ Guest8619 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)18:58
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com)19:05
- AbortRetryFail (QUIT: Quit: reboots reboots reboots) (~arf@146.ip-149-56-132.net)19:23
+ bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com)20:18
- jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)20:32
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)20:32
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com)20:41
+ bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com)20:41
+ chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1)21:13
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com)21:20
+ bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com)21:21
- gustav28 (QUIT: Quit: Quit) (~gustav@78.82.53.73)22:15
- jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)22:34
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com)22:52
+ bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com)22:52
+ jacobk (~quassel@2603:8080:b200:7b02::b71)22:54
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com)22:54
+ bkeys1 (~Thunderbi@195.sub-75-228-53.myvzw.com)22:54
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com)22:56
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)22:58
- jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@2603:8080:b200:7b02::b71)23:08
+ bkeys (~Thunderbi@134.22.115.162)23:32
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@134.22.115.162)23:42
+ bkeys (~Thunderbi@134.22.115.162)23:43
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@134.22.115.162)23:52
+ bkeys (~Thunderbi@134.22.115.162)23:53

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!