Launchpad has imported 9 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=88401.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2015-01-14T12:40:04+00:00 Pupykin-s wrote:

Steps to reproduce:
- became root
- run alsamixer, change master volume
- in another terminal run "systemctl disable qwe.socket"
master volume changes back.

It looks like systemctl disable qwe.socket cause systemctl start alsa-
restore.service

Changing sound volume is not what I expected when disabling .socket)

ArchLinux x86_64, kernel 3.18.2-2, systemd 218-1.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/0

------------------------------------------------------------------------
On 2015-01-14T12:42:41+00:00 Pupykin-s wrote:

qwe.socket does not exist, but it does not matter. Probably systemctl
disable reloads target including alsa-* services.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/1

------------------------------------------------------------------------
On 2015-01-14T14:33:00+00:00 Pupykin-s wrote:

May be the prolem is related to alsa:

/usr/lib/systemd/system/basic.target.wants contains

alsa-restore.service -> ../alsa-restore.service
alsa-state.service -> ../alsa-state.service

How to fix this issue properly?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/2

------------------------------------------------------------------------
On 2015-01-28T19:15:04+00:00 Lennart-poettering wrote:

Could you please turn on debug mode in PID with "systemd-analyze set-
log-level debug". Then please reproduce the issue and attach the logs
generated from PID 1 about this. Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/3

------------------------------------------------------------------------
On 2015-03-07T14:49:23+00:00 zbyszek wrote:

Should be fixed with
http://cgit.freedesktop.org/systemd/systemd/commit/?id=6e392c9c45.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/4

------------------------------------------------------------------------
On 2015-03-07T15:39:57+00:00 Intelfx100 wrote:

(In reply to Zbigniew Jedrzejewski-Szmek from comment #4)
> Should be fixed with
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=6e392c9c45.

Thanks for finally reviewing it :)

Is it going to be backported?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/5

------------------------------------------------------------------------
On 2015-03-07T16:40:33+00:00 zbyszek wrote:

That's really up to distributions. For Fedora, most likely.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/6

------------------------------------------------------------------------
On 2015-03-07T17:16:04+00:00 Intelfx100 wrote:

(In reply to Zbigniew Jedrzejewski-Szmek from comment #6)
> That's really up to distributions. For Fedora, most likely.

I've meant the stable branches (systemd-stable).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/7

------------------------------------------------------------------------
On 2015-03-07T18:11:37+00:00 zbyszek wrote:

(In reply to Ivan Shapovalov from comment #7)
> (In reply to Zbigniew Jedrzejewski-Szmek from comment #6)
> > That's really up to distributions. For Fedora, most likely.
> 
> I've meant the stable branches (systemd-stable).

Yes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/comments/8


** Changed in: systemd
       Status: Unknown => Fix Released

** Changed in: systemd
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1431200

Title:
  daemon-reload runs alsa-restore.service and others

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  Confirmed

Bug description:
  When systemd is reloaded (manually, upgrades), the volume is reset,
  likely using alsa-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1431200/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to