Package Details: libgdm-plymouth 42.0+r11+g4a52f026-1

Git Clone URL: (read-only, click to copy)
Package Base: gdm-plymouth
Description: Display manager and login screen with plymouth support
Upstream URL:
Licenses: GPL
Conflicts: libgdm
Provides: libgdm
Submitter: damian01w
Maintainer: Taijian
Last Packager: Taijian
Votes: 80
Popularity: 0.023787
First Submitted: 2015-03-18 02:35 (UTC)
Last Updated: 2022-04-13 18:20 (UTC)

Pinned Comments

Taijian commented on 2020-08-20 20:48 (UTC) (edited on 2022-03-31 10:53 (UTC) by Taijian)


It is no longer neccessary or recommended to use gdm-plymouth.service in place of gdm.service.

Please stick with gdm.service

Also: Please do not flag this package as out of date just because upstream released an update. This package mirrors extra/gdm, so I will only update after the devs do. Thank you for your understanding!

Latest Comments

ewout commented on 2021-12-02 10:10 (UTC) (edited on 2021-12-02 10:12 (UTC) by ewout)

@Taijian Thanks for the update to resolve the appended digit issue on this package! Please apply the same fix to the noX version as well.

Vash63 commented on 2021-11-30 13:54 (UTC)

@lawa42 - you don't fix it, you wait for the maintainer to remove the extra 1 in the package version causing it to report as out of date. You could hack fix it by increasing the version or epoch of yours but then you would never get future updates, so it's best to wait for @Taijian to fix it.

lawa42 commented on 2021-11-24 06:49 (UTC)

How do I fix this the pkgver in the buldfile is correct, but pikaur still says it is upgrading from 41.0+r15+g23ebe617-1 to 41.0+r15+g23ebe617-1.

sorry for the stupid question

zenlord commented on 2021-11-22 13:15 (UTC)

As @ewout wrote already: package version should be 41.0+r15+g23ebe617-1

ewout commented on 2021-11-15 11:44 (UTC) (edited on 2021-11-15 11:45 (UTC) by ewout)

pkgver in PKGBUILD has a extra appended digit leading to continious rebuilding when executing a AUR helper

Taijian commented on 2021-07-28 10:16 (UTC)

@devmrfitz: what is the output of meson -v? You should get 0.59.0. If you don't, then that's where your problem comes from...

Taijian commented on 2020-10-21 10:14 (UTC)

@ExaHamza: Once gdm-prime gets updated, enabling plymouth support there should be as simple as compiling it on a system that has plymouth installed, as gdm auto-configures itself for plymouth at compile time.

That said, I do not know if there are any special quirks with NVIDIA hardware, and am unable to test for that. But do give it a try and let us know! :)

ExaHamza commented on 2020-10-20 07:37 (UTC)

Hi, can you make it compatible with optimus-manager? (like gdm-prime)

eaut commented on 2020-08-21 05:54 (UTC)

The latest package versions gdm-plymouth 3.36.3-3, libgdm-plymouth 3.36.3-3, plymouth 0.9.5-4 are starting again without problems. Switched back to gdm.service too.

Taijian commented on 2020-08-20 20:48 (UTC) (edited on 2022-03-31 10:53 (UTC) by Taijian)


It is no longer neccessary or recommended to use gdm-plymouth.service in place of gdm.service.

Please stick with gdm.service

Also: Please do not flag this package as out of date just because upstream released an update. This package mirrors extra/gdm, so I will only update after the devs do. Thank you for your understanding!

Taijian commented on 2020-08-20 20:44 (UTC)

Yeah, upon checking, it turns out that most of the xxx-plymouth.service files in the plymouth package aren't really needed any more. I'm gonna update the wiki and the plymouth packages accordingly. Also sticky a comment here.

juxuanu commented on 2020-08-20 20:42 (UTC) (edited on 2020-08-20 20:42 (UTC) by juxuanu)

I can confirm. I had to substitute this package with gdm

kubrick commented on 2020-08-20 19:54 (UTC) is definitely not the issue as I can connect with normal gdm.

Taijian commented on 2020-08-20 17:45 (UTC)

OK, could everyone affected please take a look at this bug report?

If this is not your issue, I'm going to need some logs in order to debug.

juxuanu commented on 2020-08-20 16:28 (UTC)

Hello, this update broke my ability to log into my system. Not even TTY would appear. Same thing is happening as @xuanruiqi. Please don't assume we don't have up-to-date system. I am now arch-chroot into the installation and pacman -Qii pam reports 1.4.0-3 and pacman -Qii pambase reports 20200721.1-2 and pacdiff doesn't report any existing .pacnew or .pacsave

This needs to get fixed ASAP.

xuanruiqi commented on 2020-08-20 14:54 (UTC) (edited on 2020-08-20 14:57 (UTC) by xuanruiqi)

Can confirm the new update causes problems. My pam and pambase are up to date. Yet I get the splash screen freezes. I hit up to show the text boot screen, and it's just stuck on "hold until boot process finishes up".

thabulos commented on 2020-08-20 10:39 (UTC)

@Taijian, I got the splash screen freeze despite my system being up to date (yay -Syu multiple times a day). I can provide any logs if that helps.

Taijian commented on 2020-08-20 08:57 (UTC)

Regarding the latest update:

This package always assumes that it is being installed on a properly updated Arch box. I will always do my best to ensure that it works on such a system.

Anyone installing on a different system (non-up-to-date or non-Arch) should always look at commit messages to make sure that updates do not break their outdated system. Especially when commit messages mention stuff like 'new pambase' and their system does not have that.

eaut commented on 2020-08-20 06:00 (UTC)

Do the latest changes require minimum package versions for 'pambase' and 'pam' in order to function correctly? If that is the case it should be a dependency in PKGBUILD.

thabulos commented on 2020-08-20 03:37 (UTC)

Thanks @ilyaryabikin! Last update caused my desktop to hang as well and followed your instructions to get back up and running. Hopefully @Taijian will fix.

ilyaryabikin commented on 2020-08-19 23:02 (UTC) (edited on 2020-08-19 23:03 (UTC) by ilyaryabikin)

Can't enter desktop after the last update. Plymouth splash screen just freezes so I can't do anything. Switching to another TTY with no GUI also didn't help.

Installing GDM from extra repository with Live USB and deleting gdm-plymouth solved this problem for now.

coxackie commented on 2020-03-20 15:18 (UTC)

@Taijian - you are totally right, apologies.

Taijian commented on 2020-03-20 12:56 (UTC) (edited on 2020-03-20 12:57 (UTC) by Taijian)

OK, everyone who keeps flagging this as outdated: THERE IS NO NEW RELEASE OF GDM YET!

Upstream is here:

Unless something gets tagged there, it is not a release. So stop bothering me with stuff that only exists in your imagination! Thank you!

Taijian commented on 2019-10-13 18:57 (UTC)

@gedda: Well, pkgconf is part of base-devel, which is assumed installed by any and all AUR packages. So no, it really should not be in makedepends.

gedda commented on 2019-10-12 16:59 (UTC) (edited on 2019-10-12 17:01 (UTC) by gedda)

This package is missing pkgconf in it's makedepends, if prepare starts erroring with that AC_PATH_EXTRA is undefined, you are missing pkg-config.

hrniels commented on 2019-09-21 10:22 (UTC)

I just ran into the issue that prepare() assumes that the build directory does not exist. So, better add a "|| true" or use "-p".

megadriver commented on 2019-04-09 10:22 (UTC) (edited on 2019-04-09 10:40 (UTC) by megadriver)

I'm going to try that. Thanks!

Edit: Yup, that did the trick!

Taijian commented on 2019-04-09 10:22 (UTC)

@megadriver: Nope, not really... Can you try building in a clean chroot? Maybe there is some whacky interaction with some other package that you have installed.

megadriver commented on 2019-04-09 10:17 (UTC) (edited on 2019-04-09 10:21 (UTC) by megadriver)

When trying to build, I get this:

Error: Could not parse document:
 I/O  warning :  failed to load external entity "legal.xml"
 /home/repo/gdm-plymouth/src/build/../gdm/docs//C/index.docbook:84:  parser  error :  Failure to process entity legal

 /home/repo/gdm-plymouth/src/build/../gdm/docs//C/index.docbook:84:  parser  error :  Entity 'legal' not defined

Any ideas?

edrose commented on 2019-03-22 00:03 (UTC)

This package can be updated to 3.32 with minimal changes. Anyone struggling: modify the pkgver in the PKGBUILD to be 3.32.0 and change the first value in the sha256sums to be 'SKIP' and make the package - it builds the new version with no issues.

Unb0rn commented on 2019-03-18 06:37 (UTC)

Any updates on 3.32?

chenghung commented on 2018-11-14 17:11 (UTC)

I got a build error, do you have any idea how to resolve it ?

raceback (most recent call last): File "/usr/bin/g-ir-scanner", line 95, in <module> from giscanner.scannermain import scanner_main File "/usr/lib/gobject-introspection/giscanner/", line 42, in <module> from giscanner.dumper import compile_introspection_binary File "/usr/lib/gobject-introspection/giscanner/", line 33, in <module> from .gdumpparser import IntrospectionBinary File "/usr/lib/gobject-introspection/giscanner/", line 35, in <module> from .transformer import TransformerException File "/usr/lib/gobject-introspection/giscanner/", line 35, in <module> from .sourcescanner import ( File "/usr/lib/gobject-introspection/giscanner/", line 38, in <module> from giscanner._giscanner import SourceScanner as CSourceScanner ImportError: No module named 'giscanner._giscanner' make[3]: [/usr/share/gobject-introspection-1.0/Makefile.introspection:156: Gdm-1.0.gir] Error 1 make[3]: Leaving directory '/tmp/yaytmp-1000/gdm-plymouth/src/gdm-3.30.1/libgdm' make[2]: [Makefile:573: all] Error 2 make[2]: Leaving directory '/tmp/yaytmp-1000/gdm-plymouth/src/gdm-3.30.1/libgdm' make[1]: [Makefile:561: all-recursive] Error 1 make[1]: Leaving directory '/tmp/yaytmp-1000/gdm-plymouth/src/gdm-3.30.1' make: [Makefile:491: all] Error 2

edanniehues commented on 2018-10-21 21:21 (UTC)

I tried to build this without having gobject-introspection installed and it failed to build. Could you add this as a dependency?

undu commented on 2018-09-18 08:08 (UTC)

Here's the PKGBUILD I made following cg505's instructions:

It works on my system ;)

cg505 commented on 2018-09-18 05:12 (UTC)

For those upgrading to 3.30.0: it is not sufficient to just bump pkgver. You will get filesystem conflicts in pacman for /lib/udev/rules.d/61-gdm.rules. This file should be in /usr/lib/... instead. For this you need this commit, which is on master but not on a release yet. The extra/gdm build includes this commit.

cg505 commented on 2018-06-23 13:25 (UTC) is GONE! They have moved everything over to GitLab. Please update the tarball to (they also have .tar.bz2 but no .tar.xz). It seems to work after updating the source URL and checksum.

rafael.castellar commented on 2018-06-20 10:35 (UTC) (edited on 2018-06-20 10:35 (UTC) by rafael.castellar)

hi! changed the gdm source to this url, it's downloaded but could not finish the installation. It seems to be checksum problem:

==> Compilando e instalando pacote ==> Criando o pacote: gdm-plymouth 3.28.0-3 (qua 20 jun 2018 07:34:13 -03) ==> Verificando as dependências de tempo de execução... ==> Verificando as dependências de tempo de compilação... ==> Obtendo fontes... -> Encontrado gdm-gnome-3-28.tar.bz2 -> Encontrado 0002-Xsession-Don-t-start-ssh-agent-by-default.patch -> Encontrado gdm.sysusers ==> Validando source arquivos com sha256sums... gdm-gnome-3-28.tar.bz2 ... FALHOU 0002-Xsession-Don-t-start-ssh-agent-by-default.patch ... Passou gdm.sysusers ... Passou ==> ERRO: Um ou mais arquivos não passaram na verificação de validade! ==> ERRO: Makepkg não conseguiu compilar gdm-plymouth. ==> Reiniciar a compilação de gdm-plymouth ? [s/N] ==> ----------------------------------------------

liums commented on 2018-05-25 10:55 (UTC)

Hi, to install this I needed to change gdm source url to :

babel commented on 2018-05-25 02:18 (UTC)

I get this error trying to install: url: (22) The requested URL returned error: 401 Unauthorized. Maybe the url just changed...

ceaser commented on 2018-05-21 18:24 (UTC)

I updated this to 3.28.1 which appears to be just a simple version bump. if anyone wants to use it or merge it.

nullptr_t commented on 2018-03-25 16:18 (UTC)

The compiler flags where updated.

Taijian commented on 2018-03-25 11:30 (UTC)

Also, the gdm package in [extra] has changed some of the build flags in the update to 3.28.0. Maybe you want to mirror those changes in this package as well?

cg505 commented on 2018-03-25 04:19 (UTC) (edited on 2018-03-25 04:21 (UTC) by cg505)

To update to 3.28.0, it appears sufficient to just update the pkgver and checksum. I changed PKGBUILD like so:


and everything seems to be working alright.

@nullptr_t you should probably consider this a critical update, since gnome 3.28 is now in extra, and an unsuspecting user is likely to (as I did) just run pacman -Syu and they will end up with a system that does not start gdm on boot.

zhmieXD commented on 2017-11-17 12:12 (UTC) (edited on 2017-11-17 12:13 (UTC) by zhmieXD)

Has anybody installed this without problems? i get this error while building : from /tmp/yaourt-tmp-zhmie/aur-gdm-plymouth/src/gdm- /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-' make[2]: *** [Makefile:565: all] Error 2 make[2]: Leaving directory '/tmp/yaourt-tmp-zhmie/aur-gdm-plymouth/src/gdm-' make[1]: *** [Makefile:559: all-recursive] Error 1 make[1]: Leaving directory '/tmp/yaourt-tmp-zhmie/aur-gdm-plymouth/src/gdm-' 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 (UTC)

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 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 (UTC) (edited on 2017-10-30 08:36 (UTC) by nullptr_t)

I'll try to solve it.

shihjay2 commented on 2017-10-27 18:49 (UTC)

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 (UTC)

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 (UTC) (edited on 2017-10-21 21:42 (UTC) by cubethethird)

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 (UTC)

> 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 (UTC)

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

sincorchetes commented on 2017-10-11 15:00 (UTC)

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 (UTC) (edited on 2017-10-08 11:54 (UTC) by DaveB)

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 (UTC)

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

r3b311i0n commented on 2017-10-07 08:51 (UTC)

Checksum fail on gdm.sysusers

rocqua commented on 2017-08-26 08:29 (UTC)

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 (UTC) (edited on 2017-08-25 04:09 (UTC) by shihjay2)

@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:42 (UTC) (edited on 2017-08-23 21:49 (UTC) by nullptr_t)

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 (UTC)

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 (UTC)

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

fmauNeko commented on 2017-05-09 17:39 (UTC)

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 (UTC)

Any updating to 3.24?

caspian commented on 2017-03-13 15:33 (UTC)

@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 (UTC)

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

caspian commented on 2017-03-13 06:33 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

nullptr_t commented on 2016-10-26 07:28 (UTC)

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

Nexxuz commented on 2016-10-25 20:02 (UTC)

is the update coming soon?

justin8 commented on 2016-10-18 09:45 (UTC)

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 (UTC) (edited on 2016-10-12 11:04 (UTC) by frosticecold)

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 (UTC)

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

lazydays79 commented on 2016-04-18 14:00 (UTC)

@nullptr_t Thanks!

mcComBat commented on 2016-04-17 20:57 (UTC)

@nullptr_t Thanks!

nullptr_t commented on 2016-04-17 14:58 (UTC)

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 (UTC)

@shihjay2, worked great, thanks!

shihjay2 commented on 2016-04-16 18:08 (UTC) (edited on 2016-04-16 18:10 (UTC) by shihjay2)

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 (UTC)

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 (UTC)

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 (UTC)

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

shihjay2 commented on 2016-04-13 23:10 (UTC)

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 (UTC)

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

commented on 2016-04-10 21:17 (UTC)

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

edrose commented on 2016-04-10 11:46 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

I've got the repo up and running again, but the URL changed:

nullptr_t commented on 2015-12-12 17:57 (UTC)

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 (UTC) (edited on 2015-12-12 14:50 (UTC) by nullptr_t)

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 =$repo/$arch The key-id is 1607AC45 armv6h might follow when I have more time.

mrapp commented on 2015-12-03 14:06 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

jurf commented on 2015-04-19 12:15 (UTC)

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.

jurf commented on 2015-04-19 10:06 (UTC)

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 (UTC)

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

Frnco commented on 2015-04-17 05:55 (UTC)

Needs an update for 3.16, any plans on that?

oxalin commented on 2015-03-19 05:27 (UTC)

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")