Your message dated Sun, 1 Sep 2019 02:36:49 +0200
with message-id <[email protected]>
and subject line Re:
has caused the Debian Bug report #934067,
regarding
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
934067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934067
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: debian/3.12.1-1
Severity: important
Dear Maintainers,
Gdm3 package symlinks gdm3.service -> gdm.service but the next systemd
release will really dislike it and will mark services as failed:
test@test-Standard-PC-i440FX-PIIX-1996:~$ service gdm3 status
● gdm.service - GNOME Display Manager
Loaded: error (Reason: Unit gdm.service failed to load properly:
File exists.)
Active: inactive (dead)
aug 06 18:12:37 test-Standard-PC-i440FX-PIIX-1996 systemd[1]:
gdm.service: Two services allocated for the same bus name
org.gnome.DisplayManager, refusing operation.
test@test-Standard-PC-i440FX-PIIX-1996:~$ service gdm status
● gdm.service - GNOME Display Manager
Loaded: error (Reason: Unit gdm.service failed to load properly:
File exists.)
Active: inactive (dead)
aug 06 18:14:59 test-Standard-PC-i440FX-PIIX-1996 systemd[1]:
gdm.service: Two services allocated for the same bus name
org.gnome.DisplayManager, refusing operation.
This can already be observed with the systemd version in Ubuntu eoan-proposed.
Luckily GDM starts and lets users to log in, but the service is marked
as dead. This breaks systemd autopkgtest:
...
test_udev (__main__.ServicesTest) ... ok
======================================================================
ERROR: test_gdm3 (__main__.ServicesTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/tmp/autopkgtest.bVYr80/build.F0n/src/debian/tests/boot-and-services",
line 72, in test_gdm3
self.active_unit('gdm3')
File "/tmp/autopkgtest.bVYr80/build.F0n/src/debian/tests/boot-and-services",
line 183, in active_unit
out = subprocess.check_output(['systemctl', 'status', unit])
File "/usr/lib/python3.7/subprocess.py", line 395, in check_output
**kwargs).stdout
File "/usr/lib/python3.7/subprocess.py", line 487, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['systemctl', 'status',
'gdm3']' returned non-zero exit status 3.
----------------------------------------------------------------------
Ran 23 tests in 9.748s
FAILED (errors=1, skipped=2)
autopkgtest [04:15:47]: test boot-and-services: -----------------------]
boot-and-services FAIL non-zero exit status 1
Please fix the issue to let next systemd pass autopkgtest.
Cheers,
Balint
--
Balint Reczey
Ubuntu & Debian Developer
--- End Message ---
--- Begin Message ---
Closing, this was not a bug in gdm3
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
