2023-12-30.log

- murdock (QUIT: Ping timeout: 268 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)00:13
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)00:14
- ckeen (QUIT: Remote host closed the connection) (~ckeen@2001:67c:20a1:1010:db1:1c4f:a839:7bea)00:41
+ robin (~robin@user/terpri)01:55
- chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@2a02:587:7a0c:fb00:1ac0:4dff:fedb:a3f1)01:59
- sevan (QUIT: Ping timeout: 255 seconds) (~sevan@user/venture37)02:21
- b0 (QUIT: Quit: adiĆ³s) (~b0@leo.uberspace.de)02:32
+ b0 (~b0@leo.uberspace.de)02:32
- mjw (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org)02:59
- nsc (QUIT: Ping timeout: 246 seconds) (~nicolas@15-49-142-46.pool.kielnet.net)03:47
+ nsc (~nicolas@238-98-142-46.pool.kielnet.net)03:48
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)03:51
- Asmadeus (QUIT: Ping timeout: 256 seconds) (~asmadeus@240b:13:8c80:d300::42:13)04:24
+ Asmadeus (~asmadeus@240b:13:8c80:d300::42:13)04:35
- skipwich (QUIT: Remote host closed the connection) (~skipwich@user/skipwich)04:56
+ skipwich (~skipwich@user/skipwich)04:56
mhoyejosch: so04:57
mhoyeI figured out the consoleblank=60 nonsense04:58
mhoyeit turns out that the debian "laptop-mode" package has a default setting called "BATT_TERMINAL_BLANK_MINUTES" that it sets to "1" by default04:59
mhoyeso04:59
mhoyelaptop-mode uses a not-greppable variable name in a non-standard increment to set a variable and doesn't mention the name the kernel uses for that variable anywhere05:00
mhoyeso05:00
mhoyeFun times.05:00
mhoyeHaving set that variable to zero, I now have what I want.05:04
- murdock (QUIT: Ping timeout: 256 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)05:25
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)05:26
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon)06:43
+ jagtalon (~quassel@user/jagtalon)06:43
- jacobk (QUIT: Ping timeout: 245 seconds) (~quassel@47-186-95-57.dlls.tx.frontiernet.net)08:00
joschmhoye: do you mean the laptop-mode-tools package? There does not exist a laptop-mode package in Debian08:19
joschthe laptop-mode-tools package ships systemd units which i think are then responsible for setting blanking on boot?08:19
joschhow did you find out what the culprit was in the end?08:20
+ laumann__ (~quassel@2a0a-e5c0-2-2-0-c8ff-fe68-bef1.loves.ipv6.at.ungleich.ch)08:31
* laumann__ -> regain08:31
- regain (QUIT: Changing host) (~quassel@2a0a-e5c0-2-2-0-c8ff-fe68-bef1.loves.ipv6.at.ungleich.ch)08:32
+ regain (~quassel@user/laumann)08:32
* regain -> laumann08:32
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon)08:47
+ jagtalon (~quassel@user/jagtalon)08:48
- jagtalon (QUIT: Client Quit) (~quassel@user/jagtalon)08:48
+ jagtalon (~quassel@user/jagtalon)08:48
- S0rin (QUIT: Ping timeout: 255 seconds) (~S0rin@user/s0rin)09:00
+ S0rin (~S0rin@user/s0rin)09:05
- S0rin (QUIT: Ping timeout: 245 seconds) (~S0rin@user/s0rin)09:11
- eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf7231c00936417280f7d5975.dip0.t-ipconnect.de)09:13
+ eibachd (~eibachd@p200300dcf7231c01fdcc0ce5ff45b7f8.dip0.t-ipconnect.de)09:14
+ S0rin (~S0rin@user/s0rin)09:19
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin)09:28
+ S0rin (~S0rin@user/s0rin)09:30
- eibachd (QUIT: Ping timeout: 246 seconds) (~eibachd@p200300dcf7231c01fdcc0ce5ff45b7f8.dip0.t-ipconnect.de)10:45
+ eibachd (~eibachd@p200300dcf7231c008abe38b063ddc87b.dip0.t-ipconnect.de)10:46
- klardotsh (QUIT: Ping timeout: 256 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net)11:27
- eibachd (QUIT: Ping timeout: 260 seconds) (~eibachd@p200300dcf7231c008abe38b063ddc87b.dip0.t-ipconnect.de)11:33
+ eibachd (~eibachd@2a01:599:202:8968:97bb:c377:65a6:388e)11:33
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:202:8968:97bb:c377:65a6:388e)11:34
+ eibachd (~eibachd@p200300dcf7231c00b3364db0ee73ff8e.dip0.t-ipconnect.de)11:34
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf7231c00b3364db0ee73ff8e.dip0.t-ipconnect.de)12:05
+ eibachd (~eibachd@p200300dcf7231c00b8ddc33d14da6f68.dip0.t-ipconnect.de)12:06
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c00b8ddc33d14da6f68.dip0.t-ipconnect.de)12:18
+ eibachd (~eibachd@p200300dcf7231c00b8ddc33d14da6f68.dip0.t-ipconnect.de)12:19
- eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf7231c00b8ddc33d14da6f68.dip0.t-ipconnect.de)12:47
+ f_[xmpp] (fffdb90022@fases/developer/funderscore)12:56
- eery (QUIT: Ping timeout: 255 seconds) (~eery@172.97.103.152)13:01
- murdock (QUIT: Ping timeout: 246 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)13:03
+ eery (~eery@172.97.103.152)13:03
+ murdock (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)13:03
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)13:06
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)13:06
hramrachAard: if travelling to desolate places with lack of power supplies is a goal ... :-D13:15
+ Twodisbetter (2cc0e4ea1c@irc.cheogram.com)13:15
hramrachlike that's exactly the point - different people have different use cases13:16
+ eibachd (~eibachd@p200300dcf7231c00b8ddc33d14da6f68.dip0.t-ipconnect.de)13:31
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf7231c00b8ddc33d14da6f68.dip0.t-ipconnect.de)13:36
- murdock (QUIT: Ping timeout: 256 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)13:41
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)13:42
+ eibachd (~eibachd@p200300dcf7231c005a14ac508eb7d694.dip0.t-ipconnect.de)13:42
- murdock (QUIT: Ping timeout: 268 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)13:47
+ murdock (~murdock@dhcp-68-142-56-15.greenmountainaccess.net)13:50
- Twodisbetter (QUIT: Remote host closed the connection) (2cc0e4ea1c@irc.cheogram.com)14:16
- f_[xmpp] (QUIT: Remote host closed the connection) (fffdb90022@fases/developer/funderscore)14:16
- murdock (QUIT: Ping timeout: 264 seconds) (~murdock@dhcp-68-142-56-15.greenmountainaccess.net)14:19
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)14:19
- f_ (QUIT: Ping timeout: 276 seconds) (~f_@fases/developer/funderscore)14:31
+ f_[xmpp] (fffdb90022@fases/developer/funderscore)14:34
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c005a14ac508eb7d694.dip0.t-ipconnect.de)15:03
+ eibachd (~eibachd@p200300dcf7231c0069f5e5b1c1562bd4.dip0.t-ipconnect.de)15:06
- f_[xmpp] (QUIT: Ping timeout: 246 seconds) (fffdb90022@fases/developer/funderscore)15:30
- murdock (QUIT: Ping timeout: 252 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)16:06
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)16:07
- murdock (QUIT: Ping timeout: 245 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)16:11
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)16:14
- murdock (QUIT: Ping timeout: 256 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)16:25
+ murdock (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)16:26
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)16:26
+ murdock (~murdock@dhcp-68-142-56-15.greenmountainaccess.net)16:26
- XYZ (QUIT: Read error: Connection reset by peer) (~XYZ@78-80-26-245.customers.tmcz.cz)16:35
- murdock (QUIT: Ping timeout: 260 seconds) (~murdock@dhcp-68-142-56-15.greenmountainaccess.net)16:42
+ murdock (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)16:43
+ XYZ (~XYZ@78-80-26-245.customers.tmcz.cz)16:44
+ mjw (~mjw@gnu.wildebeest.org)16:44
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)16:47
+ murdock (~murdock@dhcp-68-142-56-15.greenmountainaccess.net)16:48
mhoyejosch: it's terminal-blanking.conf in /etc/laptop-mode/conf.d/16:50
mhoyeas for how, tbh I was getting really frustrated trying to figure this out. But I saw a thing Bryan Cantrill said the other day about debugging,/16:51
+ f_ (~f_@fases/developer/funderscore)16:51
mhoyeHis line was that you have to start with "what is the question you would like to _be able_ to answer about this system right now."16:51
hramrach"why does it crash?"16:52
mhoyeAnd that sort of helped me move my mindset from looking for "what is setting consoleblank in this boot process I can't really see into" to "what programs, on this machine, think they should have a say in how the console behaves."16:53
mhoye... and once I started looking at it on those terms, there it was. 16:54
hramrachit's a great heuristic when it works out16:55
mhoyeAnyway, I'm going to go figure out where laptop-mode-tools lives so I can update some code comments and make this at least greppable.16:56
joschcool, nice that you found it! :)16:57
mhoyeI learned a few things about the boot process! So that's nice. 16:57
mhoyeI have a complicated set of feelings about the number of things I've learned only because the tools and documentation adjacent to the things are garbage, but here we are.16:58
hramrachsystemd is aiming at simlyfiying the answer to the question "what programs, on this machine, think they should have a say in how something behaves" to "systemd". Then you do not need to search for the responsible software, and just check out the systemd repo16:59
joschhaha17:00
mhoyeMy opinions about systemd are basically "we put the guy in charge of linux audio in charge of init and now he works for Microsoft."17:01
- GNUmoon (QUIT: Ping timeout: 240 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)17:02
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)17:03
hramrachThe audio was fixed by different group of people doing it from scratch slightly expanding on the original concept17:04
hramrachwe need the same for init17:04
hramrachACTION goes back to some yacc shaving17:05
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c0069f5e5b1c1562bd4.dip0.t-ipconnect.de)17:36
+ eibachd (~eibachd@p200300dcf7231c0024157de0f53b72f5.dip0.t-ipconnect.de)17:37
- murdock (QUIT: Ping timeout: 245 seconds) (~murdock@dhcp-68-142-56-15.greenmountainaccess.net)17:42
+ murdock (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)17:43
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)17:44
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)17:45
+ GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon)17:49
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)17:49
+ sevan (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)19:13
- sevan (QUIT: Changing host) (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)19:13
+ sevan (~sevan@user/venture37)19:13
AbortRetryFailmhoye: big mood.19:15
- murdock (QUIT: Ping timeout: 264 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)19:59
+ murdock (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)20:00
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)20:02
+ murdock (~murdock@dhcp-68-142-56-15.greenmountainaccess.net)20:02
- murdock (QUIT: Ping timeout: 240 seconds) (~murdock@dhcp-68-142-56-15.greenmountainaccess.net)20:21
+ murdock (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)20:21
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@2600:380:5846:9109:68c4:bb70:5a36:bffa)20:22
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)20:23
+ jacobk (~quassel@47-186-95-57.dlls.tx.frontiernet.net)20:29
- murdock (QUIT: Ping timeout: 264 seconds) (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)20:57
hramrachspeaking of charging: kickstarter.com/projects/2055569666/worlds-first-240w-magsafe-3-and-usb-c-magnetic-charging-cable20:58
hramrachApparently you no longer need to be Apple to make MagSafe connectors20:58
hramrachmeaning that somebody who knows how to do connectos could do them now20:59
+ murdock (~murdock@2600:380:5a7d:bc95:34e9:e185:b575:989f)21:00
AbortRetryFailIs the patent expired, or are people just betting that they can defeat Apple in court? 21:07
AbortRetryFailTbh, I don't think the USPTO should have ever granted them a patent on that. I had counter-top kitchen appliances with magnetic attachment power cords decades before they ever made magsafe21:08
AbortRetryFailprior art what21:08
joschmy daughter has a sack to keep her feet warm inside her bike trailer in which she sits. That sack closes using magnets. There is a label on the sack that says that this is patented. It's absolutely nuts what you can patent. There are literally magnets in one side of the cloth and iron in the other. That's it.21:30
- jacobk (QUIT: Ping timeout: 268 seconds) (~quassel@47-186-95-57.dlls.tx.frontiernet.net)21:32
hramrachyou can patent swinging on a swing https://patents.google.com/patent/US6368227B1/en21:33
hramrachit's not so much about prior art as it is about hiring a lawyer that can write a convincing application - for the definition of convincing that applies to patent office clerks21:33
hramrachalso they clearly patented that specific cable, not magnetic connectors in general21:36
hramrachand like they are the company that uses trademark agains resellers of refurbished chips - there is a tiny apple logo on each hip, and if you resell it you are diminishing Apple brand recognition by selling product that Apple did not certify to be up to their standards or whatever21:39
hramrachThey don't say why they think they can make the cable. Likely the patent is expired or the cable is different enough construction to be thought to not fall under the patent. It would be problematic to pass Chinese customs otherwise. Apple licensing it is the least likely possibility unless forced by some regulation.21:43
- murdock (QUIT: Ping timeout: 260 seconds) (~murdock@2600:380:5a7d:bc95:34e9:e185:b575:989f)22:00
+ murdock (~murdock@2600:380:5a7d:bc95:34e9:e185:b575:989f)22:00
+ f_[xmpp] (fffdb90022@fases/developer/funderscore)22:00
hramrachnot sure about the situation - Apple was issued the patent in 2007, and phased out its use in 2017, incidentally at the time the patent would expire if issued for 10 years. So MagSafe3 would likely not be covered by this original patent. To muddle the waters Apple uses the MagSafe trademark for phone accessories patented recently but these are likely completely unrelated.22:02
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@2600:380:5a7d:bc95:34e9:e185:b575:989f)22:05
+ murdock (~murdock@dhcp-209-99-199-115.greenmountainaccess.net)22:05
- eibachd (QUIT: Ping timeout: 245 seconds) (~eibachd@p200300dcf7231c0024157de0f53b72f5.dip0.t-ipconnect.de)22:13
+ eibachd (~eibachd@p200300dcf7231c009ea507a9e1109e69.dip0.t-ipconnect.de)22:13
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c009ea507a9e1109e69.dip0.t-ipconnect.de)22:20
+ chomwitt (~chomwitt@ppp-94-68-4-224.home.otenet.gr)22:21
hramrachthre is also the possibility that they never intended to ship anyhing in the first place, and then patents are not a problem at all22:46
+ eibachd (~eibachd@p200300dcf7231c009ea507a9e1109e69.dip0.t-ipconnect.de)23:40
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c009ea507a9e1109e69.dip0.t-ipconnect.de)23:45
hramrachyes, it's indeed still patented, https://law.stackexchange.com/questions/8382/is-magsafe-patented-such-that-no-one-else-can-make-magnetic-power-supplies meaning anyone endeavor of making non-Apple magnetic connectors compatible with MagSafe is leagally dubious.23:58

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