[2021-09-09T00:06:47Z] <riteo> I'll go for now, bye!
[2021-09-09T00:35:29Z] <jikl> Guys I need some help with this error
[2021-09-09T00:35:33Z] <jikl> I have this after doing kiss update
[2021-09-09T00:35:39Z] <jikl> "/usr/bin/kiss: line 1953: LOGNAME: POSIX requires LOGNAME be set"
[2021-09-09T00:37:36Z] <rio6> try export LOGNAME=your_user_name before running kiss
[2021-09-09T00:39:18Z] <jikl> Thank you, I'll try!
[2021-09-09T00:39:30Z] <dilyn> what're you up to that LOGNAME isn't set 
[2021-09-09T00:39:49Z] <jikl> I guess i required a chroot restart
[2021-09-09T00:39:59Z] <jikl> escaped the chroot and re-entered it and now it works
[2021-09-09T00:40:29Z] <jikl> BTW any reason why this happens? I'm currently install KISS btw.
[2021-09-09T00:43:16Z] <dilyn> it's only happened to me when my env has become broken in some way 
[2021-09-09T00:43:18Z] <dilyn> usually in a chroot 
[2021-09-09T00:43:43Z] <jikl> oh i see
[2021-09-09T00:43:54Z] <jikl> seems like that case if for me too or i've just misconfigured something
[2021-09-09T00:44:06Z] <jikl> thanks for helping :)
[2021-09-09T01:18:12Z] <dilyn> hmhmhm I think it's time to do some breaking experiments 
[2021-09-09T01:18:14Z] <dilyn> zlib-ng here we come 
[2021-09-09T01:55:10Z] <noocsharp> well, it appears dilyn is losing it
[2021-09-09T02:08:35Z] <jikl> Hi there!
[2021-09-09T02:08:44Z] <jikl> I have another problem with mounting EFI variables
[2021-09-09T02:09:07Z] <jikl> When doing "mount -t efivarfs none /sys/firmware/efi/efivars" I get "mount: mounting none on /sys/firmware/efi/efivars failed: Resource busy"
[2021-09-09T02:09:34Z] <jikl> I've tried unmounting the EFI variables from outside the chroot (the actual ISO) but it stills gives me this message.
[2021-09-09T02:27:23Z] <dilyn> is something already mounted to /sys/firmware/efi/efivars? 
[2021-09-09T02:28:08Z] <dilyn> i lost it long, long ago noocsharp :V 
[2021-09-09T02:56:04Z] <testuser[m]> Hi
[2021-09-09T03:09:08Z] <testuser[m]> dilyn: that's weird, RAMFS_MAGIC does overflow max value of int, but the error should be surpressed by the static cast
[2021-09-09T03:09:22Z] <testuser[m]> of unsigned int *
[2021-09-09T03:15:41Z] <testuser[m]> nvm, of int only
[2021-09-09T04:12:14Z] <testuser[m]> hmm the new chromium keeps segfaulting randomly on tab closes
[2021-09-09T04:22:48Z] <GalaxyNova> testuser[m]: maybe try gdb
[2021-09-09T04:23:11Z] <testuser[m]> I did
[2021-09-09T04:23:26Z] <testuser[m]> but it didnt, and wouldnt  yield anything cuz its not a debug build
[2021-09-09T04:23:43Z] <testuser[m]> just that the problem is in the destructor views::InkDropHost::~InkDropHost()
[2021-09-09T04:25:11Z] <testuser[m]> time to find the bug in 100000 lines of cod
[2021-09-09T04:25:13Z] <testuser[m]> e
[2021-09-09T04:33:51Z] <testuser[m]> https://github.com/gentoo/gentoo/blob/master/www-client/chromium/files/chromium-93-InkDropHost-crash.patch
[2021-09-09T04:33:52Z] <testuser[m]> oh
[2021-09-09T04:33:56Z] <testuser[m]> Bruh
[2021-09-09T12:41:59Z] <rio6> this is when rust people come out and say something about memory safety
[2021-09-09T13:32:48Z] <jikl> Hello there
[2021-09-09T13:33:23Z] <jikl> While doing "gmake LLVM=1 LLVM_IAS=1 YACC=byacc menuconfig"
[2021-09-09T13:33:40Z] <jikl> I get error "initscr: no such file or directory"
[2021-09-09T13:33:57Z] <jikl> Can this problem be fixed? If can, then how?
[2021-09-09T13:33:59Z] <testuser[m]> what terminal
[2021-09-09T13:34:06Z] <jikl> Foot terminal.
[2021-09-09T13:34:06Z] <testuser[m]> all problems can be fixed
[2021-09-09T13:34:26Z] <jikl> Same happens when doing alsamixer.
[2021-09-09T13:34:27Z] <testuser[m]> `export TERM=xterm` and try, i guess ncurses cant find your terminfo
[2021-09-09T13:34:28Z] <testuser[m]> are you in chroot
[2021-09-09T13:34:38Z] <jikl> Nope im not in chroot
[2021-09-09T13:34:46Z] <jikl> ill try that..
[2021-09-09T13:35:19Z] <jikl> That fixed it!
[2021-09-09T13:35:33Z] <testuser[m]> install strace and do `strace alsamixer`, send the log it'll tell you what exact file it cant find
[2021-09-09T13:35:37Z] <testuser[m]> foot terminfo should be present
[2021-09-09T13:35:51Z] <jikl> alright
[2021-09-09T13:35:53Z] <testuser[m]> exporting as xterm is a hack, not a real fix
[2021-09-09T13:36:08Z] <testuser[m]> do that in a new terminal though
[2021-09-09T13:36:14Z] <testuser[m]> the strace
[2021-09-09T13:36:14Z] <jikl> Oh
[2021-09-09T13:36:22Z] <jikl> Okay!
[2021-09-09T13:37:03Z] <jikl> strace is currently building so it will take some time to finish
[2021-09-09T13:45:43Z] <jikl> Alright! Heres the log file: http://termbin.com/xk4x
[2021-09-09T13:46:15Z] <jikl> And you were right, the problem is related to terminfo
[2021-09-09T13:47:24Z] <testuser[m]> weird
[2021-09-09T13:47:37Z] <testuser[m]> it decides to look everywhere but not the actual terminfo path
[2021-09-09T13:48:07Z] <testuser[m]> what's the content of `find /usr/share/foot` ?
[2021-09-09T13:49:10Z] <jikl> "find: /usr/share/foot: No such file or directory" :(
[2021-09-09T13:50:48Z] <testuser[m]> Huh
[2021-09-09T13:50:52Z] <testuser[m]> foot package should install it
[2021-09-09T13:51:03Z] <testuser[m]> try rebuildin it
[2021-09-09T13:53:05Z] <jikl> Im currently rebuilding it.
[2021-09-09T13:56:08Z] <joplnk> Hey testuser, this is the alt for jikl (because it got locked for having existing nickname).
[2021-09-09T13:57:00Z] <rio6> the joy of irc
[2021-09-09T13:57:05Z] <joplnk> I've rebuilt it. Should I reboot now?
[2021-09-09T13:57:25Z] <joplnk> yes, laughter based on my pain haha
[2021-09-09T13:57:53Z] <testuser[m]> no
[2021-09-09T13:57:58Z] <joplnk> Theb?
[2021-09-09T13:58:05Z] <joplnk> Then?*
[2021-09-09T13:58:05Z] <testuser[m]> does /usr/share/foot exist now
[2021-09-09T13:58:10Z] <testuser[m]> else there is an issue in the build script
[2021-09-09T13:58:23Z] <joplnk> nah
[2021-09-09T13:59:18Z] <joplnk> Here is the output of the build file used for foot: https://termbin.com/7mcy
[2021-09-09T14:00:34Z] <testuser[m]> that's not the build file from the kiss repo
[2021-09-09T14:00:35Z] <testuser[m]> you have terminfo disabled..
[2021-09-09T14:00:55Z] <joplnk> And ehst I can for that?
[2021-09-09T14:00:58Z] <testuser[m]> https://github.com/kisslinux/repo/blob/master/wayland/foot/build this is the current one
[2021-09-09T14:01:10Z] <testuser[m]> where did you get your file from
[2021-09-09T14:01:16Z] <joplnk> Im on wyverkiss
[2021-09-09T14:03:45Z] <testuser[m]> Then just put `export TERM=xterm-256color` in ~/.profile
[2021-09-09T14:03:55Z] <joplnk> Alright
[2021-09-09T14:05:48Z] <joplnk> That worked!
[2021-09-09T14:05:56Z] <joplnk> Thanks.
[2021-09-09T14:06:16Z] <joplnk> BTW, should I open an issue for this problem?
[2021-09-09T14:08:42Z] <testuser[m]> no
[2021-09-09T14:08:50Z] <joplnk> ok
[2021-09-09T14:09:01Z] <testuser[m]> netbsd curses doesn't support terminfo or something
[2021-09-09T14:09:12Z] <joplnk> oh
[2021-09-09T14:09:41Z] <joplnk> so..
[2021-09-09T14:09:53Z] <testuser[m]> so wat
[2021-09-09T14:09:58Z] <testuser[m]> just set term to xterm
[2021-09-09T14:10:06Z] <joplnk> ok.
[2021-09-09T15:24:55Z] <omanom> @micro_O did you get that digital ocean droplet working with KISS?  
[2021-09-09T15:52:42Z] <micro_O> omanom eyup
[2021-09-09T15:53:14Z] <micro_O> was a bit painful as a failed kernel compile meant I had to destroy and start from scratch again
[2021-09-09T15:53:23Z] <omanom> last i remember it was a grub install issue?  did you end up switching to something else or was it just a quirk of their boot
[2021-09-09T15:53:26Z] <micro_O> thankfully the virt modules were only a few
[2021-09-09T15:53:41Z] <micro_O> I think grub wasn't the issue
[2021-09-09T15:53:52Z] <micro_O> I documented it somewhere, maybe will turn into a wiki article
[2021-09-09T15:54:25Z] <micro_O> key thing is, when you are in the 'rescue image', check lsmod/modprobe, and use that to determine what you need in the kernel
[2021-09-09T15:54:32Z] <micro_O> it was basically virtio stuff
[2021-09-09T15:55:12Z] <omanom> ah yeah good call.  when i made a VM in virtualbox i did something similar... fortunately the virtualbox kernel options are pretty much all explicitly labeled
[2021-09-09T15:56:26Z] <micro_O> i started a new server-focused repo for now, under @jedahan, and once that is doing what I want it to will maybe move it to kiss-community or whatever
[2021-09-09T15:56:46Z] <micro_O> that will be worked on this weekend
[2021-09-09T15:58:07Z] <micro_O> I am also fine with giving folks here shell access
[2021-09-09T15:58:48Z] <omanom> livin' the risky life :)
[2021-09-09T15:58:50Z] <micro_O> just link / message me public keys and username and i'll give access
[2021-09-09T15:59:05Z] <micro_O> omanom low-risk: i dont have nothin on there right now xD
[2021-09-09T15:59:09Z] <micro_O> and it aint my hardware
[2021-09-09T16:01:57Z] <omanom> i'm still trying to get time put aside to finish trying to install kiss onto my rpi3
[2021-09-09T16:33:13Z] <noocsharp> "rule #1: never break userspace"
[2021-09-09T16:33:41Z] <noocsharp> and yet my touchpad doesn't work on 5.14.1
[2021-09-09T16:37:09Z] <noocsharp> or 5.14.2
[2021-09-09T17:00:04Z] <jompo> Hello there!
[2021-09-09T17:00:18Z] <jompo> I'm having a question while configuring "mold"
[2021-09-09T17:00:25Z] <jompo> It says in the documentation "To verify that mold is being used, disable binary stripping (KISS_STRIP=0) and run the following command on a newly built executable."
[2021-09-09T17:00:51Z] <jompo> So do I need to make the KISS_STRIP variable permanent by putting it in ~/.profile or /etc/profile.d or I just have to do it once for verification?
[2021-09-09T17:03:24Z] <jompo> P.S. can I also know how to un-mute an audio device using .asoundrc?
[2021-09-09T17:09:17Z] <x4n> wait? is someone online?
[2021-09-09T17:09:46Z] <x4n> <hello!>
[2021-09-09T17:10:16Z] <x4n> testing kirc..
[2021-09-09T17:11:25Z] <x4n> This is alt of jompo talking
[2021-09-09T17:12:04Z] <x4n> clear
[2021-09-09T17:12:04Z] <x4n> exit
[2021-09-09T17:12:04Z] <x4n> exit()
[2021-09-09T17:18:05Z] <soliwilos> noocsharp: I'm on 5.14.1 and my touchpad is still working.
[2021-09-09T17:18:20Z] <x3n> test
[2021-09-09T17:18:30Z] <x3n> noice
[2021-09-09T17:18:36Z] <x3n> its finally working
[2021-09-09T17:24:21Z] <noocsharp> soliwilos: we almost certainly have different touchpads
[2021-09-09T17:24:35Z] <noocsharp> it doesn't work on 5.13.15 either
[2021-09-09T17:28:32Z] <soliwilos> Yeah, considered adding the possibility of different drivers.
[2021-09-09T18:07:47Z] <noocsharp> time to bisect!
[2021-09-09T19:35:40Z] <noocsharp> nvm, they just changed the name of the i2c hid option, it works fine
[2021-09-09T19:52:11Z] <Guest73> curl -s https://download.nvidia.com/XFree86/Linux-x86_64/latest.txt | awk '{ print $1 }'
[2021-09-09T19:52:31Z] <Guest73> Find out the latest version of the NVIDIA Linux driver.
[2021-09-09T20:36:53Z] <davidgarland> to clarify the install instructions for EFI stubs regarding the "loader" argument, should I write like: "efibootmgr ... --loader /vmlinuz-5.14.2 ..." if my vmlinuz is directly in boot? should the argument just be "/vmlinuz" as it is per the instructions on the wiki? should I somehow have generated an EFI directory in boot that has a ".efi" file for
[2021-09-09T20:36:54Z] <davidgarland> me to put here instead, as I see on some other sources?
[2021-09-09T21:18:06Z] <davidgarland> ..figured out some issues (PARTUUID and UUID are not the same thing, that "/" needs to be a "\") but still not able to get it to boot :S
[2021-09-09T21:18:37Z] <davidgarland> is there any definitive way to know if the mistake I'm making is in the stub itself as opposed to the kernel or vice versa
[2021-09-09T21:28:52Z] <illiliti> test, try again, test
[2021-09-09T21:28:59Z] <illiliti> this is the only way
[2021-09-09T21:30:40Z] <davidgarland> sad
[2021-09-09T21:32:47Z] <illiliti> you can boot EFI shell and then boot linux
[2021-09-09T21:34:05Z] <davidgarland> alright, I'll research that
[2021-09-09T21:35:43Z] <illiliti> https://wiki.archlinux.org/title/EFISTUB#Using_UEFI_Shell
[2021-09-09T21:35:55Z] <illiliti> shell: https://github.com/tianocore/edk2/blob/UDK2018/ShellBinPkg/UefiShell/X64/Shell.efi
[2021-09-09T21:36:35Z] <davidgarland> thank you :)
[2021-09-09T21:37:18Z] <illiliti> move Shell.efi to /boot/efi/boot/bootx64.efi
[2021-09-09T21:39:15Z] <illiliti> some info: https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#UEFI_Shell
[2021-09-09T21:40:35Z] <illiliti> this is useful too: https://wiki.archlinux.org/title/EFISTUB#Using_UEFI_directly
[2021-09-09T21:41:28Z] <illiliti> > Outdated UEFI implementations may have compatibility issues with the Linux kernel. If there is a newer version of your UEFI with bug fixes, consider flashing it with the manufacturer's recommended tool.
[2021-09-09T21:41:59Z] <illiliti> this is one of the possible reasons why efibootmgr doesn't work
[2021-09-09T21:56:09Z] <davidgarland> ouch
[2021-09-09T21:56:14Z] <davidgarland> I hope that's not the reason
[2021-09-09T21:57:02Z] <davidgarland> not because updating would be a pain, but because I bought one of the Z SKU skylake boards with the intent of using a BCLK overclock, and newer firmware locks that out
[2021-09-09T22:04:48Z] <dilyn> davidgarland: the loader is relative to the boot partition; think of your efi partition as being a rootfs for your UEFI 
[2021-09-09T22:05:39Z] <dilyn> so if you install vmlinuz to /boot/vmlinuz-5.13.1.efi, --loader should be /vmlinuz-5.13.1.efi
[2021-09-09T22:07:03Z] <dilyn> joplnk: netbsd-curses' `tic` doesn't support an option that foot uses at build time to generate terminfo; you could always make it yourself as part of the build (https://github.com/dilyn-corner/KISS-me/blob/main/wayland/foot/build)
[2021-09-09T22:07:30Z] <dilyn> or use the ncurses in kisslinux/repo because... well... it's fine xD
[2021-09-09T22:08:40Z] <dilyn> alternatively someone could implement -e for tic in netbsd-curses and then everything would be hunky dory