2023-03-03.log

- S0rin (QUIT: Ping timeout: 246 seconds) (~S0rin@user/s0rin)00:14
+ S0rin (~S0rin@user/s0rin)00:14
- bkeys (QUIT: Ping timeout: 255 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com)00:24
vkoskiv_I managed to un-bork my system :D00:47
vkoskiv_I had an oopsie and suspended while running apt upgrade00:47
vkoskiv_So it messed up initramfs and some other stuff00:47
vkoskiv_All fixed now, it boots.00:47
vkoskiv_I just had to boot off SD card, mount boot, unlock nvme, chroot over and fix the dpkg stuff and rerun update-initramfs00:48
vkoskiv_ez00:48
vkoskiv_I'm at Instanssi now, several people have asked "What is THAT"00:48
- bluerise (QUIT: Changing host) (~bluerise@p5b0ace45.dip0.t-ipconnect.de)01:01
+ bluerise (~bluerise@user/bluerise)01:01
- mtm (QUIT: Ping timeout: 268 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)01:05
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com)01:08
- ajr (QUIT: Quit: WeeChat 3.8) (~ajr@user/ajr)01:29
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40)01:32
- GNUmoon2 (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)02:01
+ GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon)02:01
chartreuseWelp decided to try suspend again to see if much changes have been made in it's stability and of course the first time trying it it resumed to just a backlit screen but blank. Kinda tempted to try and figure out the cause on that since suspend would be nice to have02:23
chartreuseDo also need to update the LPC too I think (running a fairly early version of the powersave fix still I think) but the wake issue is IIRC userland related to wayland or such02:26
joschchartreuse: https://community.mnt.re/t/standby-suspend-to-ram-mnt-reform/538/9402:31
chartreuseAh missed that in the thread, but yeah was thinking of looking into finding a more "correct" way of soving it hopefully03:02
chartreuseBut I'll set that up in the meantime03:02
chartreuseJust finished flashing the LPC again which was painless as usual at least03:03
- bluerise (QUIT: Ping timeout: 255 seconds) (~bluerise@user/bluerise)03:10
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)03:10
+ bluerise (~bluerise@pc19f87b7.dip0.t-ipconnect.de)03:10
- murdock (QUIT: Ping timeout: 248 seconds) (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)03:36
+ murdock (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)03:37
chartreuseDid notice that I've somewhat burnt in the OLED with the battery display since I was running a custom version of the keyboard controller that auto refreshed the battery status so I'd tend to leave it displaying03:39
chartreuseThink I'll make sure the screen is dimmed after a while on the oled, and maybe look at doing stuff like shifting pixels around to help prevent that03:40
chartreuseAlright intersting, finding that that sway display enable/disable trick is not working at all for me, be it in the reform-standby script, or the keybinding. I know the keybinding is working as it's fine when active, but doesn't work after a resume from suspend03:56
chartreuseIt doesn't seem to be a sway problem for me as it occurs after suspending with `systemctl suspend` at the virtual terminal as well, keyboard backlight comes on but the display is just blank, but can enter commands03:59
chartreuseInterstingly in sway/wayland I can't seem to enter commands like I can in the virtual terminal in this state04:01
- XYZ (QUIT: Ping timeout: 268 seconds) (~XYZ@37.48.0.49)04:03
+ XYZ (~XYZ@37.48.0.49)05:47
- robin (QUIT: Ping timeout: 260 seconds) (~robin@user/terpri)06:41
- ggoes (QUIT: Remote host closed the connection) (~gregf@fsf/staff/ggoes)07:50
- tarxvf (QUIT: Ping timeout: 248 seconds) (~tarxvf@mail.tarxvf.tech)07:50
+ reformer0 (~reformer@softboy.mntmn.com)07:53
- mtm (QUIT: *.net *.split) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)07:55
- buckket (QUIT: *.net *.split) (~buckket@pdp8.buckket.org)07:55
- Guest2448 (QUIT: *.net *.split) (~nicolas@48-99-142-46.pool.kielnet.net)07:55
- reformer (QUIT: *.net *.split) (~reformer@softboy.mntmn.com)07:55
- tarxvf (QUIT: *.net *.split) (~tarxvf@mail.tarxvf.tech)07:55
- xktr (QUIT: *.net *.split) (~xktr@2602:fe3d:c01:10ca:1050:1ace:0:b)07:55
- ggoes (QUIT: *.net *.split) (~gregf@fsf/staff/ggoes)07:55
- vkoskiv_ (QUIT: *.net *.split) (~vkoskiv@89-166-62-97.bb.dnainternet.fi)07:55
- XgF (QUIT: *.net *.split) (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2)07:55
- sknebel (QUIT: *.net *.split) (~quassel@v22016013254630973.happysrv.de)07:55
- doppler (QUIT: *.net *.split) (~doppler@user/doppler)07:55
* ggoes_ -> ggoes07:55
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)07:56
+ buckket (~buckket@pdp8.buckket.org)07:56
+ Guest2448 (~nicolas@48-99-142-46.pool.kielnet.net)07:56
+ xktr (~xktr@2602:fe3d:c01:10ca:1050:1ace:0:b)07:56
+ XgF (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2)07:56
+ sknebel (~quassel@v22016013254630973.happysrv.de)07:56
+ doppler (~doppler@user/doppler)07:56
- Gooberpatrol_66 (QUIT: Read error: Connection reset by peer) (~Gooberpat@user/gooberpatrol66)08:15
+ Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66)08:16
+ mtm- (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)08:33
- mtm (QUIT: Ping timeout: 248 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)08:34
+ linx (~linx@2a02:1388:9d:bc3c:4b34:86a2:dbb0:2a36)08:56
linxgood morning!08:56
+ MajorBiscuit (~MajorBisc@c-001-018-056.client.tudelft.eduvpn.nl)09:38
* wielaard -> mjw10:52
- linx (QUIT: Quit: Quit) (~linx@2a02:1388:9d:bc3c:4b34:86a2:dbb0:2a36)11:54
- mtm- (QUIT: Ping timeout: 268 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)13:04
- murdock (QUIT: Ping timeout: 268 seconds) (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)13:39
+ murdock (~murdock@mobile-107-107-56-67.mycingular.net)13:40
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@mobile-107-107-56-67.mycingular.net)13:56
+ murdock (~murdock@50.234.255.130)13:56
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)15:09
- ggoes (QUIT: Changing host) (~gregf@ool-ae2ce474.dyn.optonline.net)16:00
+ ggoes (~gregf@fsf/staff/ggoes)16:00
+ robin (~robin@user/terpri)18:10
- MajorBiscuit (QUIT: Quit: WeeChat 3.6) (~MajorBisc@c-001-018-056.client.tudelft.eduvpn.nl)18:17
- murdock (QUIT: Ping timeout: 255 seconds) (~murdock@50.234.255.130)18:24
+ murdock (~murdock@mobile-107-107-56-89.mycingular.net)18:25
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:40)19:35
- Kooda (QUIT: Ping timeout: 260 seconds) (~kooda@natsu.upyum.com)19:38
- murdock (QUIT: Read error: Connection reset by peer) (~murdock@mobile-107-107-56-89.mycingular.net)19:46
+ murdock (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)19:48
+ Kooda (~kooda@natsu.upyum.com)19:51
- murdock (QUIT: Ping timeout: 255 seconds) (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)19:57
+ murdock (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)19:57
swivelchartreuse: oled in general is pretty easily degraded, i think it's kind of expected in any scenario where you have the same high contrasting patterns displaying repeatedly... even without it being persistently on  Re: burn-in22:08
swivelmy nokia n9 developed a persistent pattern of the sms messenger UI edges, and im not much of a phone user or anything22:09
- mjw (QUIT: Killed (NickServ (GHOST command used by markw!~wielaard@gnu.wildebeest.org))) (~mjw_@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)22:13
+ wielaard (~mjw_@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)22:13
- murdock (QUIT: Ping timeout: 268 seconds) (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)22:49
+ murdock (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)22:51
- murdock (QUIT: Ping timeout: 248 seconds) (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)22:58
+ murdock (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)22:58
- murdock (QUIT: Ping timeout: 260 seconds) (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)23:12
+ murdock (~murdock@mobile-107-107-56-35.mycingular.net)23:12
- bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net)23:33

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