💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2019-09-12.txt captured on 2024-06-16 at 13:54:27.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
2019-09-12T05:04:34 #kisslinux <dylanaraps> First morning with no package updates.
2019-09-12T05:04:40 #kisslinux <dylanaraps> Even Vim didn't see a release.
2019-09-12T06:35:32 #kisslinux <dylanaraps> Seeing as there are a ton of Linux wikis out there with most of the information being "general" I think it's better for us to focus on issues/solutions themselves.
2019-09-12T06:35:51 #kisslinux <dylanaraps> Less work on my side.
2019-09-12T06:35:55 #kisslinux <dylanaraps> See: https://getkiss.org/pages/tips/
2019-09-12T06:35:59 #kisslinux <dylanaraps> (Just an example for now)
2019-09-12T06:49:55 #kisslinux <dylanaraps> Please let me know if there is anything else that should go on this page.
2019-09-12T06:50:05 #kisslinux <dylanaraps> I can't think right now.
2019-09-12T07:10:48 #kisslinux <nestman> Please let me know if there is anything else that should go on this page.
2019-09-12T07:10:58 #kisslinux <nestman> ^ from dylanaraps
2019-09-12T07:11:18 #kisslinux <dylanaraps> ???
2019-09-12T07:11:21 #kisslinux <nestman> What about the problem about `sudo`?
2019-09-12T07:11:52 #kisslinux <nestman> I can't seem to find the solution you suggested before.
2019-09-12T07:12:08 #kisslinux <dylanaraps> That's not really a general issue. For some reason your account was disabled.
2019-09-12T07:12:29 #kisslinux <dylanaraps> It was an openssl command with chpasswd.
2019-09-12T07:14:13 #kisslinux <nestman> I see.
2019-09-12T07:15:17 #kisslinux <dylanaraps> You're the first person to have this issue and I'm still unsure as to what caused it and why iy happened.
2019-09-12T07:15:32 #kisslinux <nestman> Me too.
2019-09-12T07:15:45 #kisslinux <nestman> I was also doing some tests before.
2019-09-12T07:16:20 #kisslinux <nestman> While on root account, I tried `passwd -u myuser`.
2019-09-12T07:17:08 #kisslinux <nestman> It outputted something like myuser is already unlocked.
2019-09-12T07:17:29 #kisslinux <nestman> But I still can't run sudo commands.
2019-09-12T07:20:42 #kisslinux <dylanaraps> Yeah
2019-09-12T07:20:56 #kisslinux <dylanaraps> Then `passwd` wouldn't update the field in `/etc/shadow` for some reason.
2019-09-12T08:03:12 #kisslinux <dylanaraps> NodeJS is almost supports building with Python 3.
2019-09-12T08:03:13 #kisslinux <dylanaraps> https://github.com/nodejs/node/issues/25789
2019-09-12T08:03:30 #kisslinux <dylanaraps> Once this is supported Firefox will be the only package to require Python 2 in KISS.
2019-09-12T08:03:51 #kisslinux <dylanaraps> Mozilla will take a long while to transition though...
2019-09-12T08:05:10 #kisslinux <dylanaraps> https://github.com/nodejs/TSC/issues/753#issuecomment-530360151
2019-09-12T08:05:15 #kisslinux <dylanaraps> Or not in Node's case.
2019-09-12T09:01:53 #kisslinux <dylanaraps> It begins...
2019-09-12T09:01:55 #kisslinux <dylanaraps> ➜ ls -1
2019-09-12T09:01:57 #kisslinux <dylanaraps> gtkactionbar-no-atk.patch
2019-09-12T09:01:59 #kisslinux <dylanaraps> gtkbox-no-atk.patch
2019-09-12T09:02:01 #kisslinux <dylanaraps> gtkcalendar-no-atk.patch
2019-09-12T09:02:03 #kisslinux <dylanaraps> gtkcolorplane-no-atk.patch
2019-09-12T09:02:05 #kisslinux <dylanaraps> gtkcolorscale-no-atk.patch
2019-09-12T09:02:07 #kisslinux <dylanaraps> gtkdialog-no-atk.patch
2019-09-12T09:02:09 #kisslinux <dylanaraps> gtkfilechooserwidget-no-atk.patch
2019-09-12T09:02:11 #kisslinux <dylanaraps> gtkheaderbar-no-atk.patch
2019-09-12T09:02:13 #kisslinux <dylanaraps> gtkinfobar-no-atk.patch
2019-09-12T09:02:15 #kisslinux <dylanaraps> gtkmessagedialog-no-atk.patch
2019-09-12T09:02:17 #kisslinux <dylanaraps> gtkmodelbutton-no-atk.patch
2019-09-12T09:02:19 #kisslinux <dylanaraps> gtkpathbar-no-atk.patch
2019-09-12T09:02:21 #kisslinux <dylanaraps> gtkswitch-no-atk.patch
2019-09-12T09:02:23 #kisslinux <dylanaraps> gtktoolbar-no-atk.patch
2019-09-12T09:02:25 #kisslinux <dylanaraps> ➜ grep -i atk * | wc -l
2019-09-12T09:02:27 #kisslinux <dylanaraps> 349
2019-09-12T09:02:29 #kisslinux <dylanaraps> A lot to go.
2019-09-12T09:18:21 #kisslinux <dylanaraps> OK. Builds fine thus far.
2019-09-12T09:24:01 #kisslinux <nestman> do i still need to rebuild KISS even if im using the up to date tarball?
2019-09-12T09:24:42 #kisslinux <dylanaraps> It's optional.
2019-09-12T09:24:56 #kisslinux <dylanaraps> Do it if you want to modify the CFLAGS/CXXFLAGS.
2019-09-12T09:25:10 #kisslinux <dylanaraps> Or leave it and you'll eventually rebuild everything through updates anyway.
2019-09-12T09:25:13 #kisslinux <dylanaraps> Up to you.
2019-09-12T09:33:33 #kisslinux <jml_> I'm getting a checksum error trying to build a package. what is the best way to force KISS to download new files?
2019-09-12T09:34:08 #kisslinux <dylanaraps> Which package?
2019-09-12T09:35:06 #kisslinux <dylanaraps> You can 'rm' the source in '~/.cache/kiss/sources/pkgname/`.
2019-09-12T09:35:15 #kisslinux <dylanaraps> I want to confirm that it isn't an error on my end though.
2019-09-12T09:35:34 #kisslinux <jml_> firefox
2019-09-12T09:36:46 #kisslinux <jml_> hmm same error
2019-09-12T09:36:48 #kisslinux <jml_> !> [firefox] Failed to generate checksums.
2019-09-12T09:39:07 #kisslinux <dylanaraps> I can reproduce.
2019-09-12T09:39:58 #kisslinux <dylanaraps> Pushing a fix.
2019-09-12T09:40:02 #kisslinux <dylanaraps> Pushed.
2019-09-12T09:41:25 #kisslinux <jml_> cheers. works now.
2019-09-12T10:44:37 #kisslinux <dylanaraps> wew
2019-09-12T10:44:40 #kisslinux <dylanaraps> ➜ ls -1 | wc -l
2019-09-12T10:44:42 #kisslinux <dylanaraps> 36
2019-09-12T10:44:45 #kisslinux <dylanaraps> 36 files patched so far.
2019-09-12T10:45:50 #kisslinux <dylanaraps> One step closer to an ATK free GTK3.
2019-09-12T10:50:43 #kisslinux <paradigm> Does KISS do any crypto to verify updates? A lazy grep for gpg against the tarball contents doesn't find anything in the kiss-specific bits.
2019-09-12T10:51:57 #kisslinux <dylanaraps> Package updates?
2019-09-12T10:53:13 #kisslinux <dylanaraps> Updates to the repositories happen over git which is operated by Konimex and I (2FA enabled/required).
2019-09-12T10:53:37 #kisslinux <dylanaraps> Sources downloaded from elsewhere are compared against checksums in the repository.
2019-09-12T10:54:20 #kisslinux <dylanaraps> Nothing user contributed goes in the official repositories. Everything user contributed lives in `community`.
2019-09-12T10:56:35 #kisslinux <paradigm> I had updates to the repos in mind. There's some inherent trust in the repo host and intervening connection there which could be assuaded by signing/verification. However, I can understand not wanting to add gnupg to the list of required packages. If git goes over https that might be sufficient for some users.
2019-09-12T10:57:38 #kisslinux <paradigm> If you don't mind adding gnupg to the requirements list, git does have commit signature features that could probably be added to KISS with very little additional code (outside of gnupg itself).
2019-09-12T10:58:25 #kisslinux <dylanara1> Updates do happen over https.
2019-09-12T10:58:32 #kisslinux <dylanara1> I'm lagging very badly right now.
2019-09-12T10:58:45 #kisslinux <paradigm> No worries, we can discuss this later if there's more to discuss
2019-09-12T10:58:46 #kisslinux <dylanara1> I can only see your messages by viewing the public logs.
2019-09-12T10:58:53 #kisslinux <dylanara1> It's working now.
2019-09-12T10:59:18 #kisslinux <dylanara1> So we'd GPG sign every commit right?
2019-09-12T11:00:03 #kisslinux <dylanara1> How would verification work on the user side? It'd be great if 'git pull' had an option to only pull commits signed by specific keys.
2019-09-12T11:00:09 #kisslinux <paradigm> If individual "releases" people pull have multiple commits, you could tag those and just sign those. Otherwise, yes, it'd be every commit.
2019-09-12T11:01:07 #kisslinux <dylanaraps> Commits aren't bundled into releases.
2019-09-12T11:01:22 #kisslinux <dylanaraps> The base tarball you use to install KISS is different as it contains binaries.
2019-09-12T11:01:33 #kisslinux <dylanaraps> When using 'kiss update' it just does a 'git pull'.
2019-09-12T11:01:39 #kisslinux <dylanaraps> So it'd have to be every commit.
2019-09-12T11:02:59 #kisslinux <dylanaraps> Commit signing is useless if there's nothing to prevent a non-signed commit from being pulled down from GitHub though.
2019-09-12T11:03:37 #kisslinux <dylanaraps> This would also involve bundling the public keys with the package manager (just thinking out loud).
2019-09-12T11:04:09 #kisslinux <paradigm> What I had in mind would verify the signature on HEAD after pulling. If if it doesn't check out, the minimalist solution is to just loudly error there. If you want to get fancier you could have it roll back to the last commit with a good signature.
2019-09-12T11:05:43 #kisslinux <dylanaraps> So: sign all commits, ship public keys with the package manager and check HEAD on each pull to verify the keys are in use.
2019-09-12T11:05:49 #kisslinux <dylanaraps> That's the gist of it right?
2019-09-12T11:06:00 #kisslinux <paradigm> That's what I have in mind, yes
2019-09-12T11:06:51 #kisslinux <konimex> so, what directory should we ship the publickey?
2019-09-12T11:07:20 #kisslinux <dylanaraps> I had `/usr/share/kiss` in mind.
2019-09-12T11:07:23 #kisslinux <dylanaraps> I still need to think about this though.
2019-09-12T11:07:25 #kisslinux <henlo> henlo
2019-09-12T11:07:27 #kisslinux <dylanaraps> https://help.github.com/en/articles/about-required-commit-signing
2019-09-12T11:07:38 #kisslinux <dylanaraps> We can restrict commits to signed ones on GitHub's end too.
2019-09-12T11:07:53 #kisslinux <dylanaraps> (Community will stay the same of course)
2019-09-12T11:07:56 #kisslinux <henlo> this place is way less comfy than discord
2019-09-12T11:07:59 #kisslinux <konimex> also, this would work ONLY if git is used as the repo central, but I'm thinking if rsync is used as central
2019-09-12T11:08:15 #kisslinux <konimex> but the use case doesn't exist yet so...
2019-09-12T11:08:22 #kisslinux <dylanaraps> The package manager would just skip running `git pull`.
2019-09-12T11:08:38 #kisslinux <konimex> well that was fast
2019-09-12T11:08:38 #kisslinux <dylanaraps> So you'd have no verification.
2019-09-12T11:09:27 #kisslinux <konimex> alright, back to directory
2019-09-12T11:09:30 #kisslinux <konimex> I think the public key should be shipped per repo
2019-09-12T11:09:40 #kisslinux <konimex> instead of /usr/share/kiss
2019-09-12T11:12:42 #kisslinux <dylanaraps> Well it's one git repository underneath.
2019-09-12T11:12:57 #kisslinux <dylanaraps> Or are you thinking about being able to have signed user repositories too?
2019-09-12T11:13:27 #kisslinux <konimex> yes, but gpg --import can be done from practically everywhere since gpg --verify by itself is useless without the key
2019-09-12T11:13:28 #kisslinux <konimex> yep
2019-09-12T11:14:39 #kisslinux <dylanaraps> gpg would require adding 5-6 packages to core.
2019-09-12T11:14:56 #kisslinux <konimex> well, it won't be strictly required
2019-09-12T11:14:59 #kisslinux <dylanaraps> We could use OpenBSD signify.
2019-09-12T11:15:08 #kisslinux <dylanaraps> It's very simple.
2019-09-12T11:15:12 #kisslinux <konimex> is it usable with git -s though?
2019-09-12T11:15:15 #kisslinux <dylanaraps> Though it wouldn't interface with git.
2019-09-12T11:15:17 #kisslinux <dylanaraps> Dunno
2019-09-12T11:15:22 #kisslinux <konimex> exactly
2019-09-12T11:16:33 #kisslinux <dylanaraps> We can probably do this without the gpg requirement (on the user side).
2019-09-12T11:17:00 #kisslinux <dylanaraps> - enforce gpg signing in the repository
2019-09-12T11:17:11 #kisslinux <dylanaraps> - ship the public keys in the repository
2019-09-12T11:17:25 #kisslinux <dylanaraps> - on kiss update pull the pub key and do a simple string compare.
2019-09-12T11:17:38 #kisslinux <dylanaraps> We should be able to pull the public key out of git without gpg.
2019-09-12T11:22:19 #kisslinux <dylanaraps> I need to give this a lot of thought first though.
2019-09-12T11:23:19 #kisslinux <dylanaraps> Linus said this about signing commits:
2019-09-12T11:23:21 #kisslinux <dylanaraps> > Signing each commit is totally stupid. It just means that you automate it, and you make the signature worth less. It also doesn't add any real value, since the way the git DAG-chain of SHA1's work, you only ever need one signature to make all the commits reachable from that one be effectively covered by that one. So signing each commit is simply missing the point.
2019-09-12T11:32:05 #kisslinux <paradigm> Yes, that's why I mentioned if you bundle commits it only makes sense to sign the last one
2019-09-12T11:33:09 #kisslinux <paradigm> I think your situation is different here, though
2019-09-12T11:33:43 #kisslinux <dylanaraps> As it stands currently only Konimex and I can push things to the repositories.
2019-09-12T11:34:05 #kisslinux <paradigm> Well, and github
2019-09-12T11:34:14 #kisslinux <dylanaraps> Of course.
2019-09-12T11:35:50 #kisslinux <dylanaraps> Pulls happen over https too.
2019-09-12T11:36:10 #kisslinux <dylanaraps> The only attack vector I could see is someone hijacking the repositories on GitHub.
2019-09-12T11:36:19 #kisslinux <dylanaraps> We both have 2FA enabled.
2019-09-12T11:36:38 #kisslinux <dylanaraps> There's of course the fact that Konimex and I need to be trusted.
2019-09-12T11:38:51 #kisslinux <nestman> currently building the kernel
2019-09-12T11:38:58 #kisslinux <nestman> i hope all goes well now
2019-09-12T11:39:14 #kisslinux <paradigm> My goal here was to bring the possibility to your attention, not necessarily to exert pressure. If you feel that's adequate, do feel free to continue to use it. However, I do think people would be justified in considering it inadequate. Ideally for this one wouldn't have to trust more than you and Konimex, and not assume infallibility from github and digicert. However, ideally KISS is small and
2019-09-12T11:39:20 #kisslinux <paradigm> simple; there's a fundamental trade-off there; what's worth while for your project is up to you.
2019-09-12T11:42:28 #kisslinux <dylanaraps> You're not exerting pressure, I enjoy discussion.
2019-09-12T11:43:11 #kisslinux <dylanaraps> KISS is in a different position as our repositories merely provide the means to build the software yourself.
2019-09-12T11:43:29 #kisslinux <dylanaraps> I need to think about this and what the best course of action is.
2019-09-12T11:45:05 #kisslinux <konimex> there's also gpg-ing the tarballs itself ala Arch, but that is quite a different beast
2019-09-12T11:45:15 #kisslinux <dylanaraps> Do other distributions with similar source repositories (APKBUILDS (alpine), templates (void)) sign theirs?
2019-09-12T11:45:31 #kisslinux <dylanaraps> I know they sign the resulting binaries but their source repositories are user contributed.
2019-09-12T11:45:36 #kisslinux <konimex> commit or tarball?
2019-09-12T11:46:01 #kisslinux <dylanaraps> The actual APKBUILD/template files.
2019-09-12T11:46:07 #kisslinux <konimex> iirc I don't think xbps has the capability to sign tarball
2019-09-12T11:46:12 #kisslinux <konimex> I don't think so
2019-09-12T11:46:27 #kisslinux <dylanaraps> xbps has signed repositories though I don't know if they're used.
2019-09-12T11:46:51 #kisslinux <dylanaraps> Nothing stops a bad actor from slipping something into Alpine or Void's source repositories.
2019-09-12T11:46:58 #kisslinux <konimex> ah I forgot, yes they have signed tarballs (.xbps.sig)
2019-09-12T11:46:58 #kisslinux <dylanaraps> Package signing is then useless.
2019-09-12T11:47:24 #kisslinux <dylanaraps> Especially when they have 5000+ packages with hundreds of user contributors.
2019-09-12T11:49:07 #kisslinux <konimex> however, they do reduce the attack vector (i.e. if the "bad actor" slips a rogue binary, it won't work against the signaturr)
2019-09-12T11:49:14 #kisslinux <konimex> s/signaturr/singature
2019-09-12T11:49:49 #kisslinux <dylanaraps> Of course.
2019-09-12T11:50:09 #kisslinux <dylanaraps> But if the APKBUILD/template is "infected" signing the binary is useless.
2019-09-12T11:50:53 #kisslinux <konimex> yes, that is where the "trusted" people to push to the repo comes in
2019-09-12T11:52:00 #kisslinux <dylanaraps> That is no different to us right now then no(?)
2019-09-12T11:53:34 #kisslinux <konimex> difference being xbps/alpine users don't interact directly with the template/APKBUILD
2019-09-12T11:53:38 #kisslinux <konimex> builders do
2019-09-12T11:54:17 #kisslinux <dylanaraps> Yes but something bad being slipped in and ending up in a signed binary is no different to our current situation.
2019-09-12T11:55:06 #kisslinux <konimex> well, infecting a binary can be quite easy, a whole git repo? that thing is quite resillient even without gpg
2019-09-12T11:55:25 #kisslinux <konimex> one history change and you end up recloning
2019-09-12T11:56:09 #kisslinux <dylanaraps> Exactly.
2019-09-12T11:56:48 #kisslinux <konimex> the only way possible to a rogue commit being slipped is human error
2019-09-12T11:57:00 #kisslinux <konimex> and once again, we are the weakest link
2019-09-12T11:57:54 #kisslinux <dylanaraps> This only really affects community though.
2019-09-12T12:11:06 #kisslinux <dylanaraps> I don't think we need signing at this stage and the core repositories won't see user contribution (all new packages go to `community`).
2019-09-12T12:12:14 #kisslinux <dylanaraps> Community is disabled by default and there is a disclaimer stating that it is _not_ maintained by us.
2019-09-12T13:25:21 #kisslinux <dylanaraps> So I just found out that a component in my laptop model is known to explode due to bad cooling. I've been compiling things for hours a day in 40 degree heat for the past few months.
2019-09-12T13:25:22 #kisslinux <dylanaraps> lol
2019-09-12T13:25:48 #kisslinux <dylanaraps> I must be one of the lucky few with a "good" model.
2019-09-12T13:36:08 #kisslinux <nestman> what happened?
2019-09-12T13:38:01 #kisslinux <dylanaraps> ??
2019-09-12T13:38:46 #kisslinux <nestman> in general, i mean
2019-09-12T13:38:59 #kisslinux <dylanaraps> Ah
2019-09-12T13:39:17 #kisslinux <dylanaraps> Nothing much today which is good.
2019-09-12T13:39:21 #kisslinux <dylanaraps> I need a break.
2019-09-12T13:39:46 #kisslinux <nestman> how can i send a screenshot?
2019-09-12T13:40:42 #kisslinux <nestman> break from what?
2019-09-12T13:43:40 #kisslinux <dylanaraps> Upload the image to teknik or imgur or wherever and paste the link.
2019-09-12T13:46:29 #kisslinux <nestman> building llvm, here we go again
2019-09-12T13:51:51 #kisslinux <dylanaraps> oof
2019-09-12T13:51:55 #kisslinux <dylanaraps> It takes a while huh.
2019-09-12T14:04:49 #kisslinux <konimex> huh, for some reason I'm no longer in the kiss org
2019-09-12T14:05:03 #kisslinux <konimex> dylanaraps: anything happened?
2019-09-12T14:05:09 #kisslinux <dylanaraps> I sent you an email Konimex.
2019-09-12T14:05:24 #kisslinux <konimex> which one?
2019-09-12T14:05:26 #kisslinux <konimex> ah
2019-09-12T14:05:28 #kisslinux <konimex> two secs
2019-09-12T16:05:18 #kisslinux <flippy> hey
2019-09-12T16:05:45 #kisslinux <dylanaraps> Hello
2019-09-12T16:06:05 #kisslinux <flippy> why did you shut down the chat discord server?
2019-09-12T16:07:20 #kisslinux <dylanaraps> It was always in the plans to move here fully.
2019-09-12T16:07:31 #kisslinux <flippy> i see
2019-09-12T16:07:42 #kisslinux <dylanaraps> Discord requires an account and their proprietary client to communicate.
2019-09-12T16:08:18 #kisslinux <flippy> That server has been up for quite a long time now
2019-09-12T16:08:24 #kisslinux <flippy> what made you use discord in the first place?
2019-09-12T16:09:50 #kisslinux <dylanaraps> I used to use it to communicate with my brother and his friends.
2019-09-12T16:10:25 #kisslinux <dylanaraps> Then I started a server on there to avoid being on two separate platforms.
2019-09-12T16:11:08 #kisslinux <dylanaraps> My brother stopped using it a while ago so I was only using it for my Linux server.
2019-09-12T16:11:39 #kisslinux <dylanaraps> And now we're here.
2019-09-12T16:11:49 #kisslinux <flippy> makes sense
2019-09-12T16:11:57 #kisslinux <flippy> doesn't matter much to me since i'm always in IRC anyway
2019-09-12T16:12:20 #kisslinux <dylanaraps> I haven't liked their privacy policy or requirements to communicate from the start. It just made sense at the time.
2019-09-12T16:12:46 #kisslinux <dylanaraps> IRC is good since it's "boring".
2019-09-12T16:13:02 #kisslinux <dylanaraps> What it is, is what it will continue to be.
2019-09-12T16:13:45 #kisslinux <flippy> right
2019-09-12T16:13:49 #kisslinux <saucecode> it is know that god communicated with many old testament characters via IRC
2019-09-12T16:13:57 #kisslinux <flippy> not to mention it's totally decentralized
2019-09-12T16:14:38 #kisslinux <dylanaraps> Yeah
2019-09-12T16:14:44 #kisslinux <dylanaraps> Clients are really easy to write too.
2019-09-12T16:15:03 #kisslinux <dylanaraps> I wrote a really basic one in bash.
2019-09-12T16:15:44 #kisslinux <dylanaraps> The one issue people seem to have with it is persistent history.
2019-09-12T16:16:10 #kisslinux <dylanaraps> Which is "fixed" by using a bouncer or checking public logs.
2019-09-12T16:16:11 #kisslinux <flippy> running a bouncer solves that problem
2019-09-12T16:16:48 #kisslinux <flippy> most people on discord are too lazy/don't care enough to set up ZNC
2019-09-12T16:18:04 #kisslinux <dylanaraps> Yup
2019-09-12T18:03:30 #kisslinux <jml_> My pherpherals aren't working with XORG I see this error in the logs.
2019-09-12T18:03:34 #kisslinux <jml_> 71591.608] (II) config/udev: Adding input device USB Keyboard (/dev/input/event5)
2019-09-12T18:03:36 #kisslinux <jml_> [ 71591.608] (II) No input driver specified, ignoring this device.
2019-09-12T18:03:38 #kisslinux <jml_> [ 71591.608] (II) This device may have been added with another device file.y
2019-09-12T18:03:48 #kisslinux <jml_> I've installed libinput aswell
2019-09-12T18:03:50 #kisslinux <jml_> w/o success
2019-09-12T18:04:00 #kisslinux <jml_> can anyone point me into the right direction of what the issue is?
2019-09-12T18:04:53 #kisslinux <dylanaraps> Are you in the 'input' group?
2019-09-12T18:04:53 #kisslinux <dylanaraps> (Your user)
2019-09-12T18:05:15 #kisslinux <dylanaraps> You also need xf86-input-libinput + libinput.
2019-09-12T18:22:08 #kisslinux <nestman> ➡ kiss u
2019-09-12T18:22:29 #kisslinux <nestman> fatal: .git/index: index file smaller than expected
2019-09-12T18:22:46 #kisslinux <jml_> ahh installing xf86-input-libinput fixed it. thanks dylan!
2019-09-12T18:26:45 #kisslinux <dylanaraps> Huh. No idea nestman.
2019-09-12T18:27:16 #kisslinux <dylanaraps> https://stackoverflow.com/questions/10076036/index-file-smaller-than-expected
2019-09-12T18:27:20 #kisslinux <dylanaraps> See that link.
2019-09-12T18:27:22 #kisslinux <dylanaraps> Simple fix.
2019-09-12T18:29:23 #kisslinux <nestman> how do I do it?
2019-09-12T18:29:35 #kisslinux <nestman> it's within var/db/kiss/repos
2019-09-12T18:36:27 #kisslinux <nestman> i ended up recloning the repo into var db kiss
2019-09-12T18:49:23 #kisslinux <nestman> ➡ alsamixer
2019-09-12T18:49:43 #kisslinux <nestman> cannot open mixer: No such file or directory
2019-09-12T19:31:23 #kisslinux <dylanaraps> nestman: Sounds like a kernel configuration issue.
2019-09-12T20:44:33 #kisslinux <jml_> [ 1961.039] (**) FontPath set to:
2019-09-12T20:44:35 #kisslinux <jml_> ${prefix}/share/fonts/X11/misc/
2019-09-12T20:44:45 #kisslinux <jml_> is it normal that FontPath contatins ${prefix} ?
2019-09-12T21:57:30 #kisslinux <nestman> dylanaraps: Sounds like a kernel configuration issue
2019-09-12T21:58:06 #kisslinux <nestman> nah, it was an asound.conf missing
2019-09-12T22:06:31 #kisslinux <nestman> xvidcore: cannot download (possibly wrong link)
2019-09-12T22:07:45 #kisslinux <konimex> try redownloading it
2019-09-12T22:11:14 #kisslinux <nestman> i checked the link online
2019-09-12T22:11:33 #kisslinux <nestman> it's .com, not .org
2019-09-12T22:12:33 #kisslinux <nestman> https://downloads.xvid.com/downloads/xvidcore-1.3.5.tar.bz2