| - mhoye (QUIT: Server closed connection) (~mhoye@li319-32.members.linode.com) | 00:03 | |
| + mhoye (~mhoye@li319-32.members.linode.com) | 00:03 | |
| + paperManu (~paperManu@146.71.9.156) | 00:13 | |
| + paperManu_ (~paperManu@146.71.9.156) | 00:16 | |
| - ndufresne (QUIT: Server closed connection) (~ndufresne@apple.collaboradmins.com) | 00:28 | |
| + ndufresne (~ndufresne@apple.collaboradmins.com) | 00:29 | |
| - chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:85f:9a18:1000:1ac0:4dff:fedb:a3f1) | 00:58 | |
| - mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 01:29 | |
| + bkeys (~Thunderbi@66.110.201.50) | 01:31 | |
| - bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@66.110.201.50) | 01:36 | |
| + bkeys1 (~Thunderbi@98.19.131.29) | 01:36 | |
| * bkeys1 -> bkeys | 01:38 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 02:09 | |
| - elektron (QUIT: Server closed connection) (~elektron@apoc.halo.nu) | 02:11 | |
| + elektron (~elektron@apoc.halo.nu) | 02:11 | |
| + pomel0 (~pomel0@user/pomel0) | 03:03 | |
| - kcxt (QUIT: Server closed connection) (~kcxt@postmarketOS/casey) | 03:12 | |
| + kcxt (~kcxt@postmarketOS/casey) | 03:12 | |
| + mrbcmorris_ (~mrbcmorri@1513413-static.lxtnkya3.metronetinc.net) | 03:24 | |
| - mrbcmorris (QUIT: Ping timeout: 264 seconds) (~mrbcmorri@217.180.255.234) | 03:25 | |
| - paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156) | 03:32 | |
| - paperManu_ (QUIT: Ping timeout: 276 seconds) (~paperManu@146.71.9.156) | 03:45 | |
| - dominicm (QUIT: Server closed connection) (45ee0d70e9@2a03:6000:1812:100::3e6) | 03:46 | |
| + dominicm (45ee0d70e9@2a03:6000:1812:100::3e6) | 03:47 | |
| + paperManu (~paperManu@146.71.9.156) | 04:00 | |
| - paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156) | 04:24 | |
| - marty (QUIT: Ping timeout: 245 seconds) (~marty@146.70.168.231) | 04:26 | |
| + sario528 (sario@libera/staff/owl/sario) | 04:26 | |
| + marty (~marty@146.70.168.231) | 04:26 | |
| - Sario (QUIT: Ping timeout: 630 seconds) (sario@libera/staff/owl/sario) | 04:30 | |
| - voltaire28_ (QUIT: Ping timeout: 264 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 05:30 | |
| + jn (~quassel@user/jn/x-3390946) | 06:13 | |
| + voltaire28_ (~jlafon@28.162.2.93.rev.sfr.net) | 06:32 | |
| - Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.0.129) | 06:52 | |
| + Ar|stote|is (~linx@149.210.0.129) | 06:58 | |
| - voltaire28_ (QUIT: Ping timeout: 264 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 07:17 | |
| + voltaire28_ (~jlafon@28.162.2.93.rev.sfr.net) | 08:01 | |
| - voltaire28_ (QUIT: Ping timeout: 276 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 08:11 | |
| - cararemixed (QUIT: Server closed connection) (sid724089@id-724089.helmsley.irccloud.com) | 08:37 | |
| + cararemixed (sid724089@id-724089.helmsley.irccloud.com) | 08:37 | |
| - bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@98.19.131.29) | 08:55 | |
| + TadeusTaD (tadeustad@psifactor.pl) | 08:59 | |
| - TadeusTaD (QUIT: Changing host) (tadeustad@psifactor.pl) | 09:00 | |
| + TadeusTaD (tadeustad@user/TadeusTaD) | 09:00 | |
| - violet (QUIT: Server closed connection) (~vi@user/meow/violet) | 09:12 | |
| + violet (~vi@user/meow/violet) | 09:12 | |
| - g3ist (QUIT: Server closed connection) (~g3ist@user/g3ist) | 09:27 | |
| + g3ist (~g3ist@user/g3ist) | 09:27 | |
| + chomwitt (~chomwitt@2a02:85f:9a18:1000:1ac0:4dff:fedb:a3f1) | 09:44 | |
| - switchy (QUIT: Server closed connection) (~switchy@mechboards/switchy) | 09:50 | |
| + switchy (~switchy@mechboards/switchy) | 09:50 | |
| - amatecha (QUIT: Server closed connection) (sid10006@user/amatecha) | 10:06 | |
| + amatecha (sid10006@user/amatecha) | 10:07 | |
| - amk (QUIT: Server closed connection) (~amk@user/amk) | 10:58 | |
| + amk (~amk@user/amk) | 10:58 | |
| - larme (QUIT: Server closed connection) (22544863b6@user/larme) | 11:21 | |
| + larme (22544863b6@user/larme) | 11:21 | |
| + mjw (~mjw@gnu.wildebeest.org) | 11:26 | |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:85f:9a18:1000:1ac0:4dff:fedb:a3f1) | 11:28 | |
| + siviq (~siviq@user/siviq) | 12:01 | |
| - siviq (QUIT: Client Quit) (~siviq@user/siviq) | 12:03 | |
| + paperManu (~paperManu@146.71.9.156) | 12:26 | |
| - MartiniMoe (QUIT: Server closed connection) (~quassel@user/MartiniMoe) | 12:29 | |
| + MartiniMoe (~quassel@user/MartiniMoe) | 12:30 | |
| - kop316 (QUIT: Server closed connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 13:07 | |
| + kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 13:07 | |
| - Ar|stote|is (QUIT: Ping timeout: 276 seconds) (~linx@149.210.0.129) | 13:38 | |
| - paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156) | 14:10 | |
| + paperManu (~paperManu@146.71.9.156) | 14:12 | |
| - paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@146.71.9.156) | 14:26 | |
| + voltaire28_ (~jlafon@28.162.2.93.rev.sfr.net) | 14:40 | |
| - ex-parrot (QUIT: Server closed connection) (~fincham@user/ex-parrot) | 14:40 | |
| + ex-parrot (~fincham@user/ex-parrot) | 14:40 | |
| + paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 14:41 | |
| - voltaire28_ (QUIT: Ping timeout: 245 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 14:46 | |
| - aloo_shu (QUIT: Server closed connection) (~aloo_shu@90.166.99.37) | 15:10 | |
| + aloo_shu (~aloo_shu@90.166.99.37) | 15:10 | |
| minute | josch: is there a blocker to release reform-tools with pcie_aspm=off workaround, can i help with that? | 15:19 |
|---|---|---|
| + voltaire28_ (~jlafon@28.162.2.93.rev.sfr.net) | 15:24 | |
| - iank (QUIT: Server closed connection) (~iank@fsf/staff/iank) | 15:28 | |
| minute | in the meantime i copied your instructions into a guide post to point people to https://community.mnt.re/t/tech-note-pcie-ssd-wifi-stability-fix-workaround-for-kernel-6-18/4235 | 15:28 |
| + iank (~iank@fsf/staff/iank) | 15:28 | |
| - mjw (QUIT: Killed (platinum.libera.chat (Nickname regained by services))) (~mjw@gnu.wildebeest.org) | 15:43 | |
| * Guest9572 -> mjw | 15:43 | |
| - voltaire28_ (QUIT: Ping timeout: 252 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 15:44 | |
| + Guest5566 (~mjw@gnu.wildebeest.org) | 15:44 | |
| wakest666 | I ran apt upgrade on my rk3588 Pocket and GDM3 is very broken... I was able to get to a tty and switch to greetd and then start sway, but seems a fix for this situation should be prioritised | 15:58 |
| - dodo (QUIT: Server closed connection) (~dodo@user/dodo) | 16:00 | |
| + dodo (~dodo@user/dodo) | 16:00 | |
| josch | minute: no blocker. I built this system image yesterday which includes reform-tools from git main to run pre-release tests: https://source.mnt.re/josch/reform-system-image/-/jobs/18870 | 16:05 |
| josch | wakest666: do you have the same problem with a vanilla system image? | 16:05 |
| wakest666 | the system I was upgrading from had almost nothing changed by me, only installed a handful of flatpacks | 16:11 |
| josch | wakest666: do you have some logs from journalctl? | 16:13 |
| wakest666 | this was reported in november of last year, and describes the same effect after I upgraded and restarted https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120609 | 16:15 |
| josch | wakest666: the same symptoms also occurred a few weeks ago and were due to mozjs_140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125927 | 16:18 |
| josch | you have to look at the log because the symptom itself (blinking cursor instead of gdm) can have a large number of reasons | 16:18 |
| josch | (including: javascript doesn't work) | 16:18 |
| + chomwitt (~chomwitt@2a02:85f:9a18:1000:1ac0:4dff:fedb:a3f1) | 16:19 | |
| - angelwood (QUIT: Server closed connection) (~angelwood@user/angelwood) | 16:26 | |
| + angelwood (~angelwood@user/angelwood) | 16:27 | |
| wakest666 | looking at the logs the most recent logs shows exactly the same as that but says mozjs_128 | 16:33 |
| wakest666 | but this is after logging in to sway I guess and then opening Files, so I guess we would need an older log | 16:34 |
| josch | wakest666: can you show me logs? Your system has all packages upgraded to their latest version, yes? I'm trying to reproduce the issue on rk3588 here. | 16:41 |
| wakest666 | yeah one sec | 16:41 |
| wakest666 | https://cloud.disroot.org/s/drbcsmagidsjsFR | 16:47 |
| josch | wakest666: you have in your log "undefined symbol: __aarch64_ldadd4_acq_rel, version mozjs_128" | 16:52 |
| josch | wakest666: how are you upgrading your system? Using "sudo apt upgrade"? | 16:53 |
| wakest666 | yep | 16:53 |
| josch | wakest666: could you run this command for me and send me the output: | 16:54 |
| josch | dpkg-query --showformat '${binary:Package} ${Version}\n' --show 'libmozjs*' | 16:54 |
| josch | wakest666: you should *not* upgrade a Debian unstable system with "sudo apt upgrade". Using "sudo apt upgrade" is what you do on a Debian *stable* system. On Debian unstable, you should be using "sudo apt full-upgrade". If you just use "sudo apt upgrade", apt will be very conservative and try to change as little as possible (which is what it should do on Debian stable). But in unstable, you want to use | 16:56 |
| josch | full-upgrade to make sure that old cruft is removed and give apt more liberties when changing packages. | 16:56 |
| josch | I'm asking because "mozjs_128" looks like you have a very old version of libmozjs installed and that would also explain why I cannot reproduce it with a current system image. | 16:56 |
| wakest666 | cool to hear that is probably the issue! looking at the reform handbook again to make sure I wasn't dreaming "You can either update individual packages or everything at once with one command: sudo apt upgrade." | 17:00 |
| wakest666 | so we should probably fix that in the handbook | 17:00 |
| josch | wakest666: indeed it says that in software.rst | 17:00 |
| josch | wakest666: another problem with just using "sudo apt upgrade" is that this will not auto-remove old kernels and then /boot will fill up over time and at some point the user has to manually clean up old kernel packages | 17:04 |
| josch | (which they are not told about, the error will just say: ENOSPACE on /boot) | 17:05 |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:85f:9a18:1000:1ac0:4dff:fedb:a3f1) | 17:05 | |
| wakest666 | libmozjs-128-0:arm64 128.14.0-1+b1 is what I get from your command btw | 17:06 |
| josch | wakest666: current is mozjs140 | 17:07 |
| josch | wakest666: try running "sudo apt full-upgrade" and it should be installing libmozjs-140-0 | 17:09 |
| wakest666 | error autoremover broke stuff | 17:09 |
| josch | wakest666: do you have more context? | 17:10 |
| wakest666 | ```Hmm, seems like the AutoRemover destroyed something which really | 17:12 |
| wakest666 | shouldn't happen. Please file a bug report against apt. | 17:12 |
| wakest666 | The following information may help to resolve the situation: | 17:12 |
| wakest666 | Unsatisfied dependencies: | 17:12 |
| wakest666 | reform-qcacld2-6.15.4-mnt-reform-arm64 : Depends: linux-image-6.15.4-mnt-reform-arm64 but it is not going to be installed | 17:12 |
| wakest666 | Error: Internal Error, AutoRemover broke stuff | 17:12 |
| josch | yes... that's the reform-qcacld2 hack... | 17:12 |
| josch | wakest666: you are on rk3588 and reform-check will advice you to remove the qcacld stuff because it's only needed on imx8m+ | 17:13 |
| josch | getting rid of the qcacld packages should fix this | 17:13 |
| josch | you should be able to do: sudo apt remove "reform-qcacld2*" | 17:16 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 17:20 | |
| wakest666 | yay all back and working, thanks for the help. so it seems like we probably need a warning somewhere cause the mistake I made can't be too uncommon since it literally says thats what people should do in the handbook that everyone has | 17:26 |
| minute | yeah i never remember that full-upgrade is even a thing :/ | 17:49 |
| josch | minute: if you are never using Debian stable, then you should forget "apt upgrade" completely :) | 18:05 |
| ^alex | ahoy, we got our new charger board. do we have to upgrade the syscon before we install it? we should probably upgrade the syscon anyway, it's been a long time. | 18:05 |
| minute | josch: uff! | 18:08 |
| minute | ^alex: no, shouldn't be necessary | 18:09 |
| josch | minute: re reform-tools upload, the last reform-tools version had a bug. I uploaded the likely fix and am now testing a new system image: https://source.mnt.re/josch/reform-system-image/-/jobs/18874 | 18:15 |
| + elb`` (~elb@2600:4041:6682:ea00:aec1:f6de:4d8:c723) | 18:15 | |
| - elb` (QUIT: Ping timeout: 245 seconds) (~elb@2600:4041:6682:ea00:9134:26f2:6a2e:a1dd) | 18:17 | |
| - hramrach (QUIT: Server closed connection) (~hramrach@nat2.prg.suse.com) | 18:43 | |
| + hramrach (~hramrach@nat2.prg.suse.com) | 18:44 | |
| josch | minute: in the forum some users are exchanging recipes to restore their favourite keyboard backlight color on boot. reform-power-daemon manages the keyboard backlight brightness. should it also go into the business of setting/restoring the backlight color to a user-supplied rgb value? | 19:09 |
| wakest666 | oh that would be so nice to have the color settings remembered across boots! | 19:35 |
| josch | yes, but making the color setting persistent could also be a function of the keyboard firmware instead -- the question is of architectural nature: which component should handle it? firmware or user-space? | 19:36 |
| - wakest666 (QUIT: Remote host closed the connection) (~Srain@p509936c9.dip0.t-ipconnect.de) | 19:37 | |
| - Svp (QUIT: Remote host closed the connection) (~svp@host-79-7-240-189.business.telecomitalia.it) | 19:51 | |
| * sario528 -> Sario | 20:01 | |
| + bkeys (~Thunderbi@98.19.131.29) | 20:28 | |
| - pomel0 (QUIT: Ping timeout: 264 seconds) (~pomel0@user/pomel0) | 20:32 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@98.19.131.29) | 20:33 | |
| + bkeys (~Thunderbi@98.19.131.29) | 20:33 | |
| * mjw -> Guest8838 | 21:10 | |
| - Guest8838 (QUIT: Killed (copper.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d) | 21:10 | |
| * Guest5566 -> mjw | 21:10 | |
| + Guest8838 (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d) | 21:10 | |
| + voltaire28_ (~jlafon@28.162.2.93.rev.sfr.net) | 21:14 | |
| + Svp (~svp@2002:4f07:f0bd:0:95e7:dc62:c203:a24) | 21:19 | |
| + siviq (~siviq@user/siviq) | 21:29 | |
| - siviq (QUIT: Client Quit) (~siviq@user/siviq) | 21:33 | |
| - buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org) | 21:37 | |
| + buckket (~buckket@vps.buckket.org) | 21:38 | |
| - voltaire28_ (QUIT: Ping timeout: 264 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 21:43 | |
| - paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 21:56 | |
| + voltaire28_ (~jlafon@28.162.2.93.rev.sfr.net) | 22:02 | |
| + pomel0 (~pomel0@user/pomel0) | 22:04 | |
| + paperManu (~paperManu@146.71.9.156) | 22:10 | |
| + paperManu_ (~paperManu@146.71.9.156) | 22:10 | |
| + chomwitt (~chomwitt@2a02:85f:9a18:1000:1ac0:4dff:fedb:a3f1) | 23:32 | |
| minute | josch: the persistence is already a feature in the keyboard4-fw (big keyboard), it just needs to be ported i think | 23:39 |
| josch | okay, great! | 23:39 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!