2022-01-29.log

- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p4fe73f5d.dip0.t-ipconnect.de)00:51
- ggoes (QUIT: Quit: ZNC 1.8.2+deb2+b1 - https://znc.in) (~gregf@fsf/staff/ggoes)01:06
+ ggoes (~gregf@fsf/staff/ggoes)01:12
+ bnys (~bnys@2607:fb90:b2e4:2ec9:cc31:be5b:4ab9:da2c)01:17
+ bnys_ (~bnys@172.56.42.81)01:20
- bnys (QUIT: Ping timeout: 260 seconds) (~bnys@2607:fb90:b2e4:2ec9:cc31:be5b:4ab9:da2c)01:23
- bnys_ (QUIT: Ping timeout: 256 seconds) (~bnys@172.56.42.81)01:27
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:21:21:0:100b)01:28
+ vagrantc (~vagrant@2600:3c01:e000:21:21:21:0:100e)01:33
+ erlehmann (~erle@ip5f5bf485.dynamic.kabel-deutschland.de)01:40
+ freakazoid343 (~matt@2603:9000:cf03:86c3:142e:beda:d724:cf20)01:43
- freakazoid333 (QUIT: Ping timeout: 240 seconds) (~matt@2603:9000:cf03:86c3:60a2:ba13:41c5:d22f)01:47
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:21:21:0:100e)01:51
+ bnys_ (~bnys@172.56.42.81)01:56
- bnys_ (QUIT: Client Quit) (~bnys@172.56.42.81)02:01
- _Bnu (QUIT: Read error: Connection reset by peer) (~beeanyew@89-160-120-72.cust.bredband2.com)02:43
+ _Bnu (~beeanyew@89-160-120-72.cust.bredband2.com)02:51
- Guest322 (QUIT: Ping timeout: 268 seconds) (~nicolas@i5C744701.versanet.de)04:01
+ nsc (~nicolas@i5C744F8A.versanet.de)04:02
* nsc -> Guest571704:03
- sts-q (QUIT: Ping timeout: 250 seconds) (~sts-q@91.200.108.174)04:41
+ sts-q (~sts-q@212.53.219.192)04:52
- patsavoura (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-32-252.mobile.nym.cosmote.net)08:30
+ Ar|stote|is (~linx@149-210-32-252.mobile.nym.cosmote.net)08:30
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-32-252.mobile.nym.cosmote.net)08:39
+ Ar|stote|is (~linx@149-210-32-252.mobile.nym.cosmote.net)08:39
- Ar|stote|is (QUIT: Client Quit) (~linx@149-210-32-252.mobile.nym.cosmote.net)08:41
+ Ar|stote|is (~linx@149-210-32-252.mobile.nym.cosmote.net)08:42
- Ar|stote|is (QUIT: Client Quit) (~linx@149-210-32-252.mobile.nym.cosmote.net)08:44
+ Ar|stote|is (~linx@149-210-32-252.mobile.nym.cosmote.net)08:49
- GNUmoon (QUIT: Ping timeout: 276 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)08:54
Boostisbetterso wrt to Chromium crashing my Sway session, I saw that Lukas posted on the forum about using Chromium via snap. I did that, and without needing to use any additional flags to force gpu use, I was able to start snap Chromium via rofi. It opened, and video performance is fantastic. I have the extensions reinstalled, and the whole thing is super stable. 11:13
Boostisbetterso thanks for the tip mntmn!11:13
mntmnBoostisbetter: interesting! glad you found a solution. fun fact: i've done the opposite like 2 days ago and going back to chromium 97 from debian. stability might depend on the mesa build/version11:19
BoostisbetterI think it is that as well. Since the snap version bundles its own version I'm not crashing. 11:32
BoostisbetterI spoke too soon. Running snap causes my wireless connection to continually drop. 11:35
BoostisbetterI purged snap / snapd11:53
Boostisbetterrestarted and reinstalled snapd11:53
Boostisbetterthen chromium stable instead of edge, and everything appears to be good again. 11:53
mntmni am experiencing gpu freezes with 5.17-rc1 when exercising heavy gui stuff (like ardour)12:11
mntmnam still on self built mesa though12:12
BoostisbetterYeah. Network drops keep happening when a snap is running. I'm just going to nuke it and remove snapd again. 12:22
BoostisbetterI'll just continue with Vivaldi for now. Software rendering works and isn't that big of a deal. 12:22
mntmnBoostisbetter: you don't need snapd to run chromium from the snap install12:28
mntmnjust saying12:28
mntmnhmm https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1415912:46
- sts-q (QUIT: Quit: ) (~sts-q@212.53.219.192)12:49
+ sts-q (~sts-q@212.53.219.192)12:49
mntmncc sigrid https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1477912:50
sigridnice :)12:54
bluerise:)13:04
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)13:05
- jvalleroy (QUIT: Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@li1266-111.members.linode.com)13:06
+ jvalleroy (~quassel@li1266-111.members.linode.com)13:06
Boostisbetteryeah, now the wireless card isn't working, in that I can't connect to anything. 13:16
Boostisbettervery curious, but also I'm done tinkering for now13:17
mntmnBoostisbetter: make sure you have only either connman or network-manager installed/running, and not both13:48
- natalie (QUIT: Ping timeout: 240 seconds) (~natalie@user/natalie)13:57
+ natalie (~natalie@user/natalie)14:55
- natalie (QUIT: Ping timeout: 256 seconds) (~natalie@user/natalie)15:00
+ natalie (~natalie@user/natalie)15:01
BoostisbetterI removed conman and just used gnone-command-settings or something like. 15:09
mntmngnome-control-center15:22
mntmnthat's just the frontend for networkmanager though15:22
mntmnbut ok15:22
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)15:57
- buckket (QUIT: Quit: buckket) (~buckket@pdp8.buckket.org)16:03
sigridmntmn: what does it take for hdmi to have audio?16:09
+ Christoph_ (~Christoph@p54bf692a.dip0.t-ipconnect.de)16:25
Boostisbettermntmn: so what I am seeing now is that is that the wireless connections are being deauthenticated saying that the previous authentication is not valid. 17:01
BoostisbetterIt happened after trying to use snaps. 17:01
Boostisbetterbut it sucks because I can no longer connect to a wireless connection. 17:03
mntmnsigrid: i believe maybe just activating the driver in dts... the driver is part of my port/patchset if nothing is missing there17:15
mntmnsigrid: need to check a nxp/boundary device tree file to see how they declare the hdmi audio stuff17:16
flowyBoostisbetter: that's annoying but i'm skeptical snap had anything to do with it. i don't think it would change anything related to your network configuration.17:24
flowyi had some difficulty with wifi at some point... i think i needed to ensure it was connecting to a 2.4ghz network instead of 517:25
flowybut the wifi kit that came with the reform is known to have somewhat poor reception. there have been some interesting discussions in the community forums around that. wifi signals fluctuate a lot, perhaps the signal just all of a sudden became too weak because of neighboring interference or whatever. you could try changing the channel on your network17:27
flowyreception can also be bad depending on how the wifi antenna is connected17:28
Boostisbetternah, the network auto adjust channels 17:46
Boostisbetterand no other device is having any issues right now17:46
Boostisbetterthe error messages I'm getting are that the wireless card is not able to authenticate. 17:46
BoostisbetterI really hope snaps had anything to do with the netowrk-manager17:48
Boostisbetterbecuase Chromium snap is awesome. Auto updates and is sudo isolated from the rest of the system. Plus video acceleration just works with no effort on my part. 17:49
Boostisbetternevermind, just was using Chromium via the snap and the same brokenpipe issue crashed Sway again. 17:59
+ vagrantc (~vagrant@2600:3c01:e000:21:21:21:0:100e)18:10
BoostisbetterThe wireless connections just can never authenticate18:11
BoostisbetterMan I wish I knew more about the inner workings of Linux. This is incredibly frustrating. 18:11
BoostisbetterI think the issue, is that Gnome is now 40 based, and with that came some network updates. 18:15
BoostisbetterI wish I knew how to downgrade to the previous version of networkmanager, etc. 18:15
Boostisbetterit is just weird how for 2 days I wasn't having any issues with it. 18:15
Boostisbetterand I mean things don't just change on the system. I did see snapd registering with several services, and networkmanager was one of them. As snaps need to be able to modify network status, it would make sense that they could mess up or alter network configurations18:22
Boostisbettermntmn: is there a way for me to kind of reset the network and wireless components? Something in the configuration is messed up, and I just don't see any other way. Also I understand this is Saturday, so please don't respond if you don't feel like it. We all need time off. 18:32
- xktr (QUIT: Ping timeout: 250 seconds) (~xktr@37.120.147.5)18:44
+ xktr (~xktr@37.120.147.5)18:46
Boostisbetterbut it looks like it is not accepting the mac address of my wifi card anymore. 18:54
Boostisbetterand i have no idea how to fix that. 18:54
- xktr (QUIT: Ping timeout: 256 seconds) (~xktr@37.120.147.5)18:57
+ xktr (~xktr@173.208.77.76)18:58
Boostisbettermntmn: Ok, I feel really stupid right now. My network controller VM died. And has been dead for about 7 days. This left the gateway running on basic rules, and it decided to revoke the Reform's authentication on the network. Once I restored the controller VM, I was able to connect again. 19:06
Boostisbetterand thank you everyone for telling that snap had nothing to do with it. 19:15
BoostisbetterI'm going to remove the snap and install the edge version of it again, because the stable 97 version crashed sway again, where as the 99 version did not. 19:18
Boostisbettermntmn: is it possible to use the snap with wayland rendering but also have gpu acceleration?19:39
+ savely (~savely@62.113.119.217)20:13
erlehmannyay https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14779/diffs20:58
- savely (QUIT: Quit: Client closed) (~savely@62.113.119.217)21:02
- GNUmoon (QUIT: Ping timeout: 276 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)21:24
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)21:39
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf692a.dip0.t-ipconnect.de)23:08

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