* gregor herrmann [2019-04-09 18:09 +0200]:
> On Sun, 07 Apr 2019 19:39:34 +0200, Elimar Riesebieter wrote:
>
> > > > Jordi is MIA at the moment. Tried to reach him since a few days. I
> > > > can't upload the fix myself, though...
> > > I pinged him on a different channel, but if he doesn't
On Sun, 07 Apr 2019 19:39:34 +0200, Elimar Riesebieter wrote:
> > > Jordi is MIA at the moment. Tried to reach him since a few days. I
> > > can't upload the fix myself, though...
> > I pinged him on a different channel, but if he doesn't have time I'm
> > happy to offer a sponsored upload to fix
Looking a bit further it seems that /var/lib/alsa/asound.state doesn't
exist.
That means that we are facing a chicken-egg problem here, the file will
never be created as the service is never started (and then never
stopped).
I don't know, if it helps, but I could manually create a working
* gregor herrmann [2019-04-07 18:16 +0200]:
> On Sun, 07 Apr 2019 18:05:06 +0200, Elimar Riesebieter wrote:
>
> > > There is a commit in the packaging repo which claims to fix this bug:
> > > https://salsa.debian.org/alsa-team/alsa-utils/commit/af161676131e94bbaed72f37d0c5d4c6685a119e
> > Jordi
On Sun, 07 Apr 2019 18:05:06 +0200, Elimar Riesebieter wrote:
> > There is a commit in the packaging repo which claims to fix this bug:
> > https://salsa.debian.org/alsa-team/alsa-utils/commit/af161676131e94bbaed72f37d0c5d4c6685a119e
> Jordi is MIA at the moment. Tried to reach him since a few
* gregor herrmann [2019-04-07 17:46 +0200]:
> Control: tag -1 + patch pending
>
> On Mon, 25 Mar 2019 12:05:36 +0100, Laurent Bigonville wrote:
>
> > The more obvious solution would of course be to remove the condition in the
> > .service file
>
> There is a commit in the packaging repo which
Control: tag -1 + patch pending
On Mon, 25 Mar 2019 12:05:36 +0100, Laurent Bigonville wrote:
> The more obvious solution would of course be to remove the condition in the
> .service file
There is a commit in the packaging repo which claims to fix this bug:
On Mon, 25 Mar 2019 12:01:02 +0100 Laurent Bigonville
wrote:
>
> An option might be to create an empty file in the postinst script on the
> first installation. An empty file will cause the "alsa restore" command
> to fail with return code 99 but the systemd service will still be marked
> as
Package: alsa-utils
Version: 1.1.8-1
Severity: important
File: /lib/systemd/system/alsa-restore.service
Hi,
On my newly installed laptop, the volume is never saved and restored
It seems that the "alsa-restore.service" is never "started/stopped"
because there is a condition not met:
$ systemctl
9 matches
Mail list logo
