Package Details: gdm-plymouth 3.26.2.1-2

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.704229
First Submitted: 2015-03-18 02:35
Last Updated: 2017-11-06 08:23

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

zhmieXD commented on 2017-11-17 12:12

Has anybody installed this without problems?
i get this error while building :

from /tmp/yaourt-tmp-zhmie/aur-gdm-plymouth/src/gdm-3.26.2.1/libgdm/g-ir-cpp-gwjnv_kk.c:4:
/usr/include/features.h:376:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
# warning _FORTIFY_SOURCE requires compiling with optimization (-O)
^~~~~~~
GICOMP Gdm-1.0.gir

(g-ir-compiler:9007): GVFS-WARNING **: can't init metadata tree /home/zhmie/.local/share/gvfs-metadata/root: open: Permission denied
/bin/sh: line 1: 9007 Trace/breakpoint trap (core dumped) /usr/bin/g-ir-compiler --includedir=. Gdm-1.0.gir -o Gdm-1.0.typelib
make[3]: *** [/usr/share/gobject-introspection-1.0/Makefile.introspection:172: Gdm-1.0.typelib] Error 133
make[3]: Leaving directory '/tmp/yaourt-tmp-zhmie/aur-gdm-plymouth/src/gdm-3.26.2.1/libgdm'
make[2]: *** [Makefile:565: all] Error 2
make[2]: Leaving directory '/tmp/yaourt-tmp-zhmie/aur-gdm-plymouth/src/gdm-3.26.2.1/libgdm'
make[1]: *** [Makefile:559: all-recursive] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-zhmie/aur-gdm-plymouth/src/gdm-3.26.2.1'
make: *** [Makefile:489: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build gdm-plymouth.

lazydays79 commented on 2017-11-05 18:21

For months I'm not able to update gdm-plymouth... what is happening here?

Making all in common
make[2]: Entering directory '/tmp/yaourt-tmp-michael/aur-gdm-plymouth/src/gdm-3.26.1/common'
CC libgdmcommon_la-gdm-address.lo
CC libgdmcommon_la-gdm-common.lo
CC libgdmcommon_la-gdm-profile.lo
CC libgdmcommon_la-gdm-settings.lo
CC libgdmcommon_la-gdm-settings-backend.lo
CC libgdmcommon_la-gdm-settings-desktop-backend.lo
CC libgdmcommon_la-gdm-settings-utils.lo
CC libgdmcommon_la-gdm-settings-direct.lo
CC libgdmcommon_la-gdm-log.lo
CCLD libgdmcommon.la
CC test-log.o
CCLD test-log
make[2]: Leaving directory '/tmp/yaourt-tmp-michael/aur-gdm-plymouth/src/gdm-3.26.1/common'
Making all in daemon
make[2]: Entering directory '/tmp/yaourt-tmp-michael/aur-gdm-plymouth/src/gdm-3.26.1/daemon'
GEN gdm-display-glue.h
Traceback (most recent call last):
File "/bin/gdbus-codegen", line 41, in <module>
from codegen import codegen_main
ImportError: cannot import name 'codegen_main'
make[2]: *** [Makefile:1190: gdm-display-glue.h] Error 1
make[2]: Leaving directory '/tmp/yaourt-tmp-michael/aur-gdm-plymouth/src/gdm-3.26.1/daemon'
make[1]: *** [Makefile:559: all-recursive] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-michael/aur-gdm-plymouth/src/gdm-3.26.1'
make: *** [Makefile:489: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build gdm-plymouth.
==> Restart building gdm-plymouth ? [y/N]
==> -------------------------------------
==>

nullptr_t commented on 2017-10-30 08:28

I'll try to solve it.

shihjay2 commented on 2017-10-27 18:49

An update to my `gdm.service: Two services allocated for the same bus name org.gnome.DisplayManager, refusing operation.` error. It turns out that fwupd is calling gdm.service. The 2 fixes are either remove gdm.service from /usr/lib/systemd/system when gdm-plymouth is updated or installed OR update the fwupd.service file to call gdm-plymouth.service in the Before section instead of gdm.service. I can imagine other packages expecting gdm.service instead of gdm-plymouth.service; is there any downside to changing the gdm-plymouth.service to overwrite the gdm.service file instead of having both in the directory to reduce this conflict?

lazydays79 commented on 2017-10-21 21:51

I'm still not able to compile it, this error comes up now since a week ago or sth:

Making all in daemon
make[2]: Verzeichnis „/tmp/yaourt-tmp-michael/aur-gdm-plymouth/src/gdm-3.26.1/daemon“ wird betreten
GEN gdm-display-glue.h
Traceback (most recent call last):
File "/bin/gdbus-codegen", line 41, in <module>
from codegen import codegen_main
ModuleNotFoundError: No module named 'codegen'
make[2]: *** [Makefile:1190: gdm-display-glue.h] Fehler 1
make[2]: Verzeichnis „/tmp/yaourt-tmp-michael/aur-gdm-plymouth/src/gdm-3.26.1/daemon“ wird verlassen
make[1]: *** [Makefile:559: all-recursive] Fehler 1
make[1]: Verzeichnis „/tmp/yaourt-tmp-michael/aur-gdm-plymouth/src/gdm-3.26.1“ wird verlassen
make: *** [Makefile:489: all] Fehler 2

cubethethird commented on 2017-10-21 21:42

During the process of building GDM, while making the docs, part of the process seems to require downloading some large (>1.5 GB) file, and does this for each locale.
What's worse is that this is all stored in RAM, so if multi-threading is used for make, it may bog down the system by using a ton of memory.

nullptr_t commented on 2017-10-14 12:44

> Your package gdm-plymouth [1] has been flagged out-of-date by dinnymate [2]:
>
> It does not build

It builds fine with `yaourt -S gdm-plymouth` and `pacaur -S gdm-plymouth`.
I removed the outdated flag.

nullptr_t commented on 2017-10-12 13:09

automake is in base-devel, which is assumed to be installed for building packages from AUR

sincorchetes commented on 2017-10-11 15:00

Need add automake as dependency to build, because It does not compile.

autoreconf: running: aclocal -I m4 ${ACLOCAL_FLAGS} --output=aclocal.m4t
sh: aclocal: command not found
autoreconf: aclocal failed with exit status: 127

DaveB commented on 2017-10-08 10:40

gdm.sysusers checksum is wrong.
Instead of:
d665e8f82ea2f6b03147223c04ca53ddb02eb3f550e3cf54dc96a44e50fb811d
it should be:
6d9c8e38c7de85b6ec75e488585b8c451f5d9b4fabd2a42921dc3bfcc4aa3e13

It installs after that.

Ups, Haeckle beat me to it :)

haeckle commented on 2017-10-07 10:28

Correct checksum for gdm.sysusers (the last one in the PKGBUILD) is 6d9c8e38c7de85b6ec75e488585b8c451f5d9b4fabd2a42921dc3bfcc4aa3e13

r3b311i0n commented on 2017-10-07 08:51

Checksum fail on gdm.sysusers

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?

caspian commented on 2017-03-13 06:33

I'm having the following compile errors with the latest update (3.22.3-1):

./configure: line 20504: syntax error near unexpected token `0.9.12'
./configure: line 20504: `GOBJECT_INTROSPECTION_CHECK(0.9.12)'

Any ideas?

nullptr_t commented on 2016-11-27 09:51

Did you try using 'pacman -Rs gdm-plymouth'? That removes all remaining unnessecary dependencies for a package.

electricprism commented on 2016-11-26 22:57

For some reason installing gdm and removing gdm-plymouth libgdm-plymouth remains. This can cause issues since it's easy to assume libgdm was installed aswell instead of just gdm.

ralt commented on 2016-11-02 11:20

Recently, I'm unable to update my arch with this error:

error: failed to prepare transaction (could not satisfy dependencies)
:: gdm-plymouth: installing gnome-shell (3.22.1+2+g5a08886-1) breaks dependency 'gnome-shell<3.21.0'

Can this package be updated to work with gnome-shell 3.22?

groundhack commented on 2016-10-31 02:57

There is something wrong with the source. Getting stuck at fetching origin

nullptr_t commented on 2016-10-26 07:28

Update 3.22.1 is online. I first updated like in the main repositories

Nexxuz commented on 2016-10-25 20:02

is the update coming soon?

justin8 commented on 2016-10-18 09:45

I'm getting the following when trying to build this in a clean chroot:

19:41:54 checking for XLIB... yes
19:41:54 checking for GTK... no
19:41:54 configure: error: Package requirements (gtk+-3.0 >= 2.91.1
19:41:54 ) were not met:
19:41:54
19:41:54 Package 'gdk-3.0' requires 'gio-unix-2.0 >= 2.49.4' but version of gio-unix-2.0 is 2.48.2
19:41:54

frosticecold commented on 2016-10-12 10:53

Was failing to upgrade to gnome 3.22

Currently reinstalled and edited the pkg build,
Replaced this string 'gnome-shell<3.21.0'
TO 'gnome-shell'

Upgrading atm, will post if everything works fine.

EDIT:

Everything works fine.
Edited the pkg build with previous line and everything 100%

Vistaus commented on 2016-09-25 08:08

Please update to 3.22, I miss this so much on 3.22 :-(

lazydays79 commented on 2016-04-18 14:00

@nullptr_t Thanks!

mcComBat commented on 2016-04-17 20:57

@nullptr_t Thanks!

nullptr_t commented on 2016-04-17 14:58

Sorry for the inconvenience. I updated the dependency to work for a full release version like 3.20.*

lazydays79 commented on 2016-04-17 08:42

@shihjay2, worked great, thanks!

shihjay2 commented on 2016-04-16 18:08

In the meantime while we wait for the maintainer to fix the package, reinstall gdm-plymouth and edit PKGBUILD at the line
depends=('plymouth' 'gnome-shell=3.20.0' 'gnome-session' 'upower' 'xorg-xrdb' 'xorg-server' 'xorg-server-xwayland' 'xorg-xhost')
and change to
depends=('plymouth' 'gnome-shell>=3.20.0' 'gnome-session' 'upower' 'xorg-xrdb' 'xorg-server' 'xorg-server-xwayland' 'xorg-xhost')

Once it is reinstalled, then you can update gnome-shell.

lazydays79 commented on 2016-04-16 17:31

So anything new about the dependency to gnome-shell?

I can't do an update since a couple of days:

:: Synchronizing package databases...
core 121.0 KiB 1247K/s 00:00 [##############################] 100%
extra 1749.6 KiB 6.65M/s 00:00 [##############################] 100%
community 3.4 MiB 9.39M/s 00:00 [##############################] 100%
multilib 161.7 KiB 11.3M/s 00:00 [##############################] 100%
archlinuxfr 11.3 KiB 1891K/s 00:00 [##############################] 100%
error: failed to prepare transaction (could not satisfy dependencies)
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: gdm-plymouth: installing gnome-shell (3.20.1-1) breaks dependency 'gnome-shell=3.20.0'

justin8 commented on 2016-04-15 23:58

Probably add a <= as well so that it will block gnome shell 3.22 updates until it's ready; but get rid of the exact version match on 3.20.0

mcComBat commented on 2016-04-15 19:34

@shihjay2 +1
Getting dependency issue when trying to update gnome-shell

shihjay2 commented on 2016-04-13 23:10

Recommend changing dependency to gnome-shell to use >= instead of = as another recent update to gnome-shell recently caused upgrading to stop due to a dependency error.

nullptr_t commented on 2016-04-11 07:37

Updated and added versioned dependency to gnome-shell. I hope I'll be fast enough when gnome gets updated.

nathan1015 commented on 2016-04-10 21:17

@edrose: +1
I had to build a local package for 3.20 today...

edrose commented on 2016-04-10 11:46

Would it be possible to make the current version of gnome-shell a dependency to prevent the problems I just had when gnome-shell upgraded without this package?

nullptr_t commented on 2016-03-09 11:00

I wonder why...this package is the same as the one in the main repos except for `--without-plymouth` left out from configure parameters.

Did you enable gdm-plymouth.service from the plymouth package?

seglberg commented on 2016-03-08 16:00

For what it's worth, I had to revert to the standard gdm package because my external monitors would not wake up after blanking when using gdm-plymouth.

nullptr_t commented on 2016-01-08 20:50

I've got the repo up and running again, but the URL changed:
https://wiki.archlinux.org/index.php/Unofficial_user_repositories#nullptr_t

nullptr_t commented on 2015-12-12 17:57

NOTE: If you are using my mirror, the repo name changed to nullptr_t to reflect username change

nullptr_t commented on 2015-12-10 21:02

You can now get this package prebuild, signed and secured from my repo here by adding the following to /etc/pacman.conf

[nullptr_t]
SigLevel = Optional TrustedOnly
Server = https://www.slau.me/archlinux/mirrors/$repo/$arch

The key-id is 1607AC45
armv6h might follow when I have more time.

mrapp commented on 2015-12-03 14:06

@somepaulo: I faced the same issue. Removing libgdm-plymouth with pacman -Rdd and afterwards reinstalling it together with gdm-plymouth also solved it for me. Thank you.

somepaulo commented on 2015-12-02 17:35

An error occurs on upgrading/installing this package (libgdm-plymouth), like so:

install: cannot stat ‘/tmp/yaourt-tmp-username/aur-libgdm-plymouth/src/org.gnome.login-screen.gschema.xml’: No such file or directory
==> ERROR: A failure occurred in package_libgdm-plymouth().
Aborting...
==> ERROR: Makepkg was unable to build gdm-plymouth.

Tried removing and reinstalling to no avail.
Ended up uninstalling libgdm-plymouth with pacman -Rdd, and built both packages successfully from gdm-plymouth.

nullptr_t commented on 2015-08-10 21:12

Thats a good question. Probably because I didn't know that the gnome developers also tag unstable versions and only versions in an own branch are considered stable.

I changed the sources back to 3.16.2 and will take care that I'm not using dev releases again.

Mayzie commented on 2015-08-10 11:46

Why is this using experimental GDM sources, and not that of stable (at the time of writing, 3.16)?

ework commented on 2015-05-01 23:50

This package shows up as orphaned by yaourt because it has no maintainer. Is there a reason for that?

DoctorJellyface commented on 2015-04-19 12:15

OK, installed, because my laptop wouldn't boot after the plymouth update without this. The screen no longer blanks out between plymouth and GDM, but now the plymouth screen just freezes and waits for GDM.

DoctorJellyface commented on 2015-04-19 10:06

Thanks for the update! Before I install, what does this package actually do? Smooth transition from Plymouth to GDM?

damian01w commented on 2015-04-18 17:57

Sorry for the delay. I'm working on it now. I will update it as soon as possible.

damian01w commented on 2015-04-18 17:55

Sorry for the delay. I'm working on with now.

Frnco commented on 2015-04-17 05:55

Needs an update for 3.16, any plans on that?

oxalin commented on 2015-03-19 05:27

It seems to be in conflict with libgdm (without plymouth support).

You should probably add something like the following to the PKGBUILD:
conflicts=('libgdm')

I don't know if it is compatible with libgdm, but if so, you could also add:
replaces=('libgdm')
provides=("libgdm=$pkgver libgdm-plymouth=$pkgver")