2022-12-01.log

- bkeys (QUIT: Ping timeout: 268 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com)00:03
- bleb (QUIT: Ping timeout: 248 seconds) (~cm@user/bleb)00:03
+ bleb_ (~cm@user/bleb)00:05
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)01:01
+ reform6941 (~bnys@c-73-239-119-220.hsd1.wa.comcast.net)01:17
* reform6941 -> bnys01:17
bnysso i did an upgrade today and now it seems like the old type of gpu glitch with green dots in gnome is no more...only to be replaced with glitching in youtube videos occasionally01:18
bnysseems like gpu acceleration in chromium is getting better though?01:19
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-4-166.mobile.nym.cosmote.net)01:24
+ Ar|stote|is (~linx@149-210-4-166.mobile.nym.cosmote.net)01:24
bnysi love sway but i love some of the little things that gnome has: kb input switcher (i type in japanese sometimes) and a soft power switch01:54
bnysunfortunately sleep appears to be busted again womp womp01:55
bnysmight need to try a new image at this point tho01:55
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)02:02
- bnys (QUIT: Remote host closed the connection) (~bnys@c-73-239-119-220.hsd1.wa.comcast.net)02:05
+ bkeys (~Thunderbi@75-174-122-101.boid.qwest.net)02:52
+ JC[m] (~jclibremo@2001:470:69fc:105::2:ce68)02:52
- bkeys (QUIT: Ping timeout: 268 seconds) (~Thunderbi@75-174-122-101.boid.qwest.net)04:11
+ chartreus (~chartreus@S0106f0f249dfd9c3.cg.shawcable.net)06:56
+ dustfing` (~user@d75-159-228-218.abhsia.telus.net)06:57
+ iank_ (~iank@fsf/staff/iank)06:58
+ tadeus_brick (tadeustad@psifactor.pl)06:59
+ violet_ (~vi@user/violet)07:00
- violet (QUIT: *.net *.split) (~vi@user/violet)07:05
- chartreuse (QUIT: *.net *.split) (~chartreus@s0106f0f249dfd9c3.cg.shawcable.net)07:05
- iank (QUIT: *.net *.split) (~iank@fsf/staff/iank)07:05
- dustfinger (QUIT: *.net *.split) (~user@d75-159-228-218.abhsia.telus.net)07:05
- TadeusTaD (QUIT: *.net *.split) (tadeustad@psifactor.pl)07:05
- XgF (QUIT: *.net *.split) (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2)07:05
+ chartreuse (~chartreus@S0106f0f249dfd9c3.cg.shawcable.net)07:11
- chartreus (QUIT: Read error: Connection reset by peer) (~chartreus@S0106f0f249dfd9c3.cg.shawcable.net)07:12
+ bgs (~bgs@212-85-160-171.dynamic.telemach.net)07:14
- bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net)07:53
+ chomwitt (~chomwitt@2a02:587:7a0c:6a00:1ac0:4dff:fedb:a3f1)08:12
+ XgF (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2)08:34
+ MajorBiscuit (~MajorBisc@86-88-79-148.fixed.kpn.net)09:11
- chartreuse (QUIT: Quit: Leaving) (~chartreus@S0106f0f249dfd9c3.cg.shawcable.net)09:22
- S0rin (QUIT: Ping timeout: 260 seconds) (~S0rin@user/s0rin)09:41
+ S0rin (~S0rin@user/s0rin)09:45
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin)09:51
+ S0rin (~S0rin@user/s0rin)09:51
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)09:54
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin)10:05
- MajorBiscuit (QUIT: Ping timeout: 252 seconds) (~MajorBisc@86-88-79-148.fixed.kpn.net)10:06
+ S0rin (~S0rin@user/s0rin)10:09
- chomwitt (QUIT: Remote host closed the connection) (~chomwitt@2a02:587:7a0c:6a00:1ac0:4dff:fedb:a3f1)10:13
+ chomwitt (~chomwitt@2a02:587:7a0c:6a00:1ac0:4dff:fedb:a3f1)10:14
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)10:51
- S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin)10:51
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)10:52
+ S0rin (~S0rin@user/s0rin)10:57
+ MajorBiscuit (~MajorBisc@145.15.244.234)11:10
- GNUmoon (QUIT: Ping timeout: 255 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)11:36
- buckket (QUIT: Read error: Connection reset by peer) (~buckket@pdp8.buckket.org)11:37
- MajorBiscuit (QUIT: Ping timeout: 252 seconds) (~MajorBisc@145.15.244.234)11:41
+ buckket (~buckket@pdp8.buckket.org)11:42
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin)11:43
+ S0rin (~S0rin@user/s0rin)11:54
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)12:12
+ MajorBiscuit (~MajorBisc@ip-185-104-137-32.ptr.icomera.net)12:18
- mjw (QUIT: Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))) (~mark@gnu.wildebeest.org)13:06
* wielaard -> mjw13:06
+ mark_ (~mark@gnu.wildebeest.org)13:06
- MajorBiscuit (QUIT: Ping timeout: 268 seconds) (~MajorBisc@ip-185-104-137-32.ptr.icomera.net)14:23
- XYZ (QUIT: Remote host closed the connection) (~XYZ@78-80-26-181.customers.tmcz.cz)16:33
+ XYZ (~XYZ@78-80-26-181.customers.tmcz.cz)16:44
- XYZ (QUIT: Remote host closed the connection) (~XYZ@78-80-26-181.customers.tmcz.cz)16:48
+ XYZ (~XYZ@78-80-26-181.customers.tmcz.cz)16:49
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com)16:50
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)18:07
flowyjust did an apt upgrade, and Xwayland is now segfaulting. i'd guess it has something to do with the new libc6 package18:12
flowythe only thing i desperately need is rofi. turns out there's a fork supporting wayland. so far it works perfectly as a drop-in replacement.18:14
flowyhttps://github.com/lbonn/rofi#wayland-support18:14
minuteoof. do we have to rebuild our packages josch?19:06
minuteflowy: maybe you can try to remove the xwayland package from mntre and install the default one from debian?19:06
minutesoon we can get rid of it anyway because of new fixes in mesa/etnaviv19:07
flowypersonally i'm good, in a way i kind of like Xwayland being broken so i can figure out how to become wayland exclusive :)19:20
joschflowy: is your xwayland version 2:22.1.5-1+reform1?19:22
joschflowy: when did you upgrade? I upgraded on the 29th and i didn't see any segfaults19:23
joschflowy: do you have steps to reproduce the segfault you see?19:23
flowy22.1.5-1+reform1 yes19:24
flowyapt upgraded roughly 2 hours ago19:25
joschflowy: can you show me the last parts of your /var/log/apt/history.log19:25
joschflowy: the segfaults happens when you run rofi?19:26
josch(rofi works fine for me)19:26
flowylibc6 package: 2.36-619:27
joschi have 2.36-519:27
flowyyeah, rofi segfaulted or anything else using Xwayland19:27
flowyXwayland segfaults and the backtrace stops at libc619:28
joschaha, let me quickly update my libc6 to see if i can reproduce it19:28
joschno segfault -- let me restart sway as well just to be sure19:30
joschflowy: nope, no segfault with libc6 2.36-619:32
joschflowy: what other packages were upgraded?19:32
joschor what other libraries are part of your backtrace?19:32
flowyi'll put the backtrace into a pastebin19:33
joschflowy: and your /var/log/apt/history.log maybe?19:34
joschit would be useful to know the set of packages that got upgraded19:34
joschor maybe a paste of what the following command prints: dpkg-query --showformat '${binary:Package}=${Version}\n' --show19:35
flowyaha, well, i had XWAYLAND_NO_GLAMOR=1 in my env (some tweak i made some months back because without it a bunch of apps were unuseable)19:35
flowyi tried unsetting that19:35
flowyand now it doesn't segfault19:35
joschXWAYLAND_NO_GLAMOR=1 rofi -show drun -display-drun -theme mnt-reform -font "Inter Bold 24"19:36
joschdoesn't segfault here :D19:36
joschah maybe i need to have set that at the point when sway starts...19:36
flowyprobably needs to be exported19:37
+ ajr (~ajr@user/ajr)19:38
joschnope, even with sway (and thus my whole graphical session) running with XWAYLAND_NO_GLAMOR=1 there is no segfault19:38
flowyso it might be a different package causing the issue19:39
joschyes, maybe19:39
joschdid your upgrade include anything mesa related?19:39
flowyseems so. i'll trim my dpkg.log to today and pastebin it19:40
flowyor is history.log more informative?19:41
joschthe information in apt's log is more readable :)19:41
joschwe don't need the state changes from dpkg log -- we just need to know what got installed in the end19:42
joschdoing tail -6 /var/log/apt/history.log should get you what you want (the last apt operation)19:42
minuteXWAYLAND_NO_GLAMOR=1 is an env var for xwayland, not for the application19:43
joschminute: but xwayland is started by sway so if i start sway with that variable set, that should start xwayland with that variable set19:44
joschmy /proc/$(pgrep Xwayland)/environ confirms that xwayland is running with XWAYLAND_NO_GLAMOR=1 set19:46
flowythe upgrade https://pastebin.com/1sbU25SB19:47
flowythe backtrace https://pastebin.com/vWspsnbN19:49
flowyjosch: cool trick w /proc/, need to remember that one19:50
flowyah so i see i was probably misinterpreting that backtrace. :)19:54
joschflowy: it's mesa19:54
josch22.3.0-1 was uploaded 2 hours ago19:54
joschand if you have that installed then also having XWAYLAND_NO_GLAMOR=1 set makes rofi segfault19:55
joschif you downgrade to 22.2.4-1 then setting XWAYLAND_NO_GLAMOR=1 does nothing19:55
- bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com)19:57
minutejosch: correct @ variable20:29
+ bkeys (~Thunderbi@192.225.189.50)20:38
- bkeys (QUIT: Ping timeout: 260 seconds) (~Thunderbi@192.225.189.50)22:04
+ bkeys (~Thunderbi@192.225.189.50)22:10
- bkeys (QUIT: Ping timeout: 256 seconds) (~Thunderbi@192.225.189.50)23:21

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