11:12 <luca020400> latest chrome crashes...

11:12 <luca020400> [ 116.452236] ThreadPoolForeg[4009]: segfault at 101e ip 000056536727db32 sp 00007f413772b460 error 4 in chrome[56535f89e000+822b000]

11:12 <luca020400> nice

11:14 <luca020400> oh wow

11:15 <luca020400> some shit in network stack

11:17 <luca020400> the heck

11:17 <luca020400> now even old version dies

11:18 <LuK1337> you can always use firefox

11:19 <luca020400> I will

11:19 <luca020400> just bothers me

11:22 <luca020400> new version likely made some breaking changes to saved data

11:22 <luca020400> that's why old crashes

11:26 <luca020400> so I guess killing systemd-resolved is the solution for now

12:05 <luca020400> LuK1337: can you cat /etc/resolv.conf

12:06 <luca020400> unless fedora is also using systemd-resolved

12:10 <LuK1337> pretty sure i already talked with you about that...

12:10 <LuK1337> check your weechat logs

12:10 <LuK1337> nothing changed since then

12:13 <luca020400> ak ok

12:13 <luca020400> you're affected as well then

12:13 <luca020400> latest systemd + chrome = no good

12:13 <luca020400> just in case you update

12:13 <LuK1337> i don't think that fedora is going to do that...

12:14 <LuK1337> i'd think that fedora has bit higher stability standards

12:14 <LuK1337> and someone would block systemd update that breaks chrome

12:15 <luca020400> the problem is that the new systemd update was released before chrome...

12:15 <luca020400> and old chrome is just fine

12:16 <luca020400> but yeah, it was reported 20 days ago

12:41 <luca020400> nice chromium bug

12:42 <luca020400> they forgot to add a null check

12:44 <luca020400> whut

12:44 <luca020400> someone broke fn keys

12:48 <luca020400> what

12:48 <luca020400> how

12:48 <luca020400> https://github.com/torvalds/linux/commit/ce357fd34f94bb5aff5443987c1e4fd39b8aae37

12:48 <luca020400> I did this

12:48 <luca020400> but how

12:50 <luca020400> wow

12:50 <luca020400> I did break it somehow

12:50 <luca020400> [ 157.460492] asus_wmi: `false' invalid for parameter `fnlock_default'

12:50 <luca020400> I must be an idot

12:50 <luca020400> options module_name parameter_name=parameter_value

12:51 <luca020400> so 1/0

12:51 <LuK1337> kinda expected

12:51 <luca020400> yeah I'm an idiot

12:51 <luca020400> no idea why I saved false

12:51 <luca020400> my local modprobe has 0

12:51 <luca020400> xD

12:52 <luca020400> ok welcome back fn keys