Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Am 03.02.20 um 08:18 schrieb Yves-Alexis Perez: > So, if I do that, lightdm.service is not installed at all (it comes from > debian/, not the upstream sources). You can install debian/lightdm.service via debian/lightdm.install. signature.asc Description: OpenPGP digital signature

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2020-02-02 at 21:08 +0100, Yves-Alexis Perez wrote: > > An empty > > override_dh_installsystemd: > > > > is probably better suited in this case. > > > > Not sure if this fixes the issue you are seeing, just something I > > noticed while

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Am 02.02.20 um 21:08 schrieb Yves-Alexis Perez: > On Sun, 2020-02-02 at 21:03 +0100, Michael Biebl wrote: >> I had a very superficial look at debian/rules > >> override_dh_installsystemd: >>dh_installsystemd -plightdm --no-start -r lightdm.service > >> I suppose you don't want that. > >

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2020-02-02 at 21:03 +0100, Michael Biebl wrote: > I had a very superficial look at debian/rules > > override_dh_installsystemd: >dh_installsystemd -plightdm --no-start -r lightdm.service > > I suppose you don't want that. To be

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Am 02.02.20 um 20:45 schrieb Michael Biebl: > Am 02.02.20 um 16:13 schrieb Yves-Alexis Perez: >> On Sat, 2020-02-01 at 03:21 +0100, Michael Biebl wrote: >>> They should also add a >> >>> [Install] >>> Alias=display-manager.service >> >>> section >> >>> to their service file. Which will make sure

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Am 02.02.20 um 20:45 schrieb Michael Biebl: > Am 02.02.20 um 16:13 schrieb Yves-Alexis Perez: >> On Sat, 2020-02-01 at 03:21 +0100, Michael Biebl wrote: >>> They should also add a >> >>> [Install] >>> Alias=display-manager.service >> >>> section >> >>> to their service file. Which will make sure

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Am 02.02.20 um 16:13 schrieb Yves-Alexis Perez: > On Sat, 2020-02-01 at 03:21 +0100, Michael Biebl wrote: >> They should also add a > >> [Install] >> Alias=display-manager.service > >> section > >> to their service file. Which will make sure that if you run >> "systemctl enable foo.service",

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2020-02-01 at 03:21 +0100, Michael Biebl wrote: > They should also add a > > [Install] > Alias=display-manager.service > > section > > to their service file. Which will make sure that if you run > "systemctl enable foo.service",

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Control: retitle -1 Improve handling of display-manager.service symlink Control: clone -1 -2 -3 -4 -5 -6 -7 Control: reassign -1 gdm3 Control: reassign -2 lightdm Control: reassign -3 sddm Control: reassign -4 lxdm Control: reassign -5 xdm Control: reassign -6 slim Control: reassign -7 wdm On

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

¡Hola! El 2014-11-24 a las 13:37 +0100, Didier Roche escribió: -DEFAULT_SERVICE=/etc/systemd/system/display-manager.service +DEFAULT_SERVICE=display-manager.service +SERVICE=$(basename $(cat "$DEFAULT_DISPLAY_MANAGER_FILE")).service # set default-display-manager systemd service link according

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

On Mon, 24 Nov 2014 09:23:22 +0100 Didier Roche wrote: > Le 22/11/2014 21:28, Andrei POPESCU a écrit : > > > > 2b. Each display manager must add a Conflicts=[all other DMs] > > You don't really need to maintain a long list of Conflicts (which will > never be kept up to

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Le 22/11/2014 21:28, Andrei POPESCU a écrit : 2b. Each display manager must add a Conflicts=[all other DMs] You don't really need to maintain a long list of Conflicts (which will never be kept up to date). I suggested last wek to the gdm maintainers that we start using the Alias. That

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Here is an updated version of the patch (ensuring we echo a warning if systemctl enable fails) after discussing with Laurent. There seems to be one case failing due to the autogenerated gdm3 service script from the LSB version which is making systemctl enable --force gdm3 failing,

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

On Vi, 10 oct 14, 00:10:18, Andrei POPESCU wrote: On Jo, 09 oct 14, 17:55:18, Andrei POPESCU wrote: I have to run 'dpkg-reconfigure lightdm' to have lightdm's postinst recreate the display-manager.service symlink, which is not obvious. Actually that wasn't enough to re-enable lightdm,

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

Package: systemd Version: 215-5+b1 Severity: normal Hi, # systemctl disable lightdm Synchronizing state for lightdm.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d lightdm defaults Executing /usr/sbin/update-rc.d lightdm disable insserv: warning: current start

Bug#764607: systemd: systemctl does not re-create display-manager.service symlink

On Jo, 09 oct 14, 17:55:18, Andrei POPESCU wrote: I have to run 'dpkg-reconfigure lightdm' to have lightdm's postinst recreate the display-manager.service symlink, which is not obvious. Actually that wasn't enough to re-enable lightdm, in the end I had to resorte to 'dpkg --purge