Github messages for voidlinux
 help / color / mirror / Atom feed
From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pulseaudio: update to 15.0.
Date: Wed, 28 Jul 2021 19:22:23 +0200	[thread overview]
Message-ID: <20210728172223.qC1Z_ZtOPfvHPLiL_zLiIrVPysEUWgHO8q3UTw4ZkHs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32232@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

New comment by steinex on void-packages repository

https://github.com/void-linux/void-packages/pull/32232#issuecomment-888484469

Comment:
> Maybe try disabling lto? Unlikely to actually fix it, just a first step in debugging.

That actually fixed it. I disabled LTO for `arm*` now.

> What does the elogind functionality bring? Just to have an idea if enabling it is really worth it.

It gives each login session a PA client. I'm not sure what that actually means or what it's good for, however you added this comment in the last update: "`XXX: new version should be able to enable systemd functionality using elogind`".

I would be fine to leave it disabled.

  parent reply	other threads:[~2021-07-28 17:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 16:12 [PR PATCH] " steinex
2021-07-28 16:39 ` ericonr
2021-07-28 16:40 ` ericonr
2021-07-28 17:01 ` ericonr
2021-07-28 17:03 ` [PR PATCH] [Updated] " steinex
2021-07-28 17:22 ` steinex [this message]
2021-07-28 17:25 ` steinex
2021-07-28 17:36 ` steinex
2021-07-28 17:38 ` steinex
2021-07-28 17:39 ` steinex
2021-08-24 23:11 ` [PR REVIEW] " abenson
2021-08-25  0:49 ` [PR PATCH] [Closed]: " abenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210728172223.qC1Z_ZtOPfvHPLiL_zLiIrVPysEUWgHO8q3UTw4ZkHs@z \
    --to=steinex@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).