Package Details: gdm-plymouth 3.24.2-1

Git Clone URL: https://aur.archlinux.org/gdm-plymouth.git (read-only)
Package Base: gdm-plymouth
Description: Gnome Display Manager with Plymouth support.
Upstream URL: http://www.gnome.org
Licenses: GPL
Groups: gnome
Conflicts: gdm
Provides: gdm
Submitter: damian01w
Maintainer: nullptr_t
Last Packager: nullptr_t
Votes: 55
Popularity: 0.462020
First Submitted: 2015-03-18 02:35
Last Updated: 2017-08-16 07:18

Pinned Comments

nullptr_t commented on 2017-08-23 21:44

If you USE PLYMOUTH in your initcpio for now:
* Enable gdm-plymouth.service

If you DON'T USE PLYMOUTH in your initcpio for now:
* Enable gdm.service

Latest Comments

rocqua commented on 2017-08-26 08:29

Fixed on a second run without making any changes, but on my first run, this failed with error:

./configure: no such file found

It seems that somehow makepkg decided not to extract the source files. This is when installing with pacaur. It's probably nothing, but I figured I'd report it anyway.

shihjay2 commented on 2017-08-25 04:02

@nullptr_t, I had already confirmed that I disabled gdm.service prior to seeing the error after I updated gdm-plymouth. I also have called plymouth in initcpio. I have been using the gdm-plymouth package for some time now and it was only with the recent update that this error started showing up. I have verified already that the display-manager.service (which is designated when you enable gdm-plymouth.service) is pointing to gdm-plymouth.service which is correct. However, the existence of the gdm.service file (I don't have gdm package installed) in /usr/lib/systemd/system is causing systemd to call it for some reason (I don't know why since it's not enabled) and deleting it is the only way for the error to go away. BTW, I only use one display manager - gdm.

nullptr_t commented on 2017-08-23 21:44

If you USE PLYMOUTH in your initcpio for now:
* Enable gdm-plymouth.service

If you DON'T USE PLYMOUTH in your initcpio for now:
* Enable gdm.service

nullptr_t commented on 2017-08-23 21:42

To fix your problem: Disable gdm.service and gdm-plymouth.service and enable just one of them, there is no need for deletion of files.
(Example: You did something like enabling two display managers like lightdm and gdm at the same time)

The package plymouth provides systemd services for most display managers (e.g. gdm-plymouth.service) with dependencies to plymouth-quit.service and similar, while gdm provides one itself.

shihjay2 commented on 2017-08-19 13:12

I'm getting a startup error in my logs `gdm.service: Two services allocated for the same bus name org.gnome.DisplayManager, refusing operation.`. Even though the gdm package was uninstalled, there is a gdm.service file in /usr/lib/systemd/system that gets placed during the AUR package install. Deleting the gdm.service file fixes the problem as the gdm-plymouth.service file is already being referenced by display-manager.service

nullptr_t commented on 2017-05-09 17:46

Thank you :) Is patched out with the current pkgrel.

fmauNeko commented on 2017-05-09 17:39

I'm getting configure: WARNING: unrecognized options: --with-authentication-agent-directory, --without-consolekit, --with-systemd, and indeed, those options disappeared from the official gdm PKGBUILD.
Otherwise builds fine !

wat commented on 2017-04-09 02:22

Any updating to 3.24?

caspian commented on 2017-03-13 15:33

@nullptr_t: It compiled after I cleared all of the pacaur cache files. Not sure why, but it did the trick. Thanks

nullptr_t commented on 2017-03-13 09:38

3.22.3-1 compiles fine for me. Does the error persist on a subsequent try?

All comments