@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.
Search Criteria
Package Details: libgdm-plymouth 42.0+r11+g4a52f026-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/gdm-plymouth.git (read-only, click to copy) |
---|---|
Package Base: | gdm-plymouth |
Description: | Display manager and login screen with plymouth support |
Upstream URL: | https://wiki.gnome.org/Projects/GDM |
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) |
Dependencies (10)
- libgio-2.0.so (lib32-glib2-git, glib2-selinux, glib2-nodocs-git, glib2-git, glib2-patched-thumbnailer, glib2, lib32-glib2)
- libglib-2.0.so (lib32-glib2-git, glib2-selinux, glib2-nodocs-git, glib2-git, glib2-patched-thumbnailer, glib2, lib32-glib2)
- libgobject-2.0.so (lib32-glib2-git, glib2-selinux, glib2-nodocs-git, glib2-git, glib2-patched-thumbnailer, glib2, lib32-glib2)
- libsystemd.so (systemd-libs-homed-containers, systemd-libs-selinux, systemd-libs-git, systemd-pr23511-libs, systemd-libs)
- docbook-xsl (make)
- git (git-git, git-vfs, git-run-command-patch-git) (make)
- gobject-introspection (gobject-introspection-git) (make)
- meson (meson-git) (make)
- yelp-tools (make)
- check (check-git) (check)
Required by (11)
- ebadoo-shell (requires libgdm)
- gdm-git (requires libgdm)
- gdm-plymouth
- gdm-prime (requires libgdm)
- gnome-initial-setup-git (requires libgdm)
- gnome-shell-338 (requires libgdm)
- gnome-shell-git (requires libgdm)
- gnome-shell-oldstable (requires libgdm)
- gnome-shell-perf (requires libgdm)
- gnome-shell-performance (requires libgdm)
- gnome-shell-xrdesktop-git (requires libgdm)
Sources (2)
Latest Comments
ewout commented on 2021-12-02 10:10 (UTC) (edited on 2021-12-02 10:12 (UTC) by ewout)
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)
Attention
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)
https://bugs.archlinux.org/task/67636 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?
https://bugs.archlinux.org/task/67636?project=1&order=dateopened&sort=desc
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: https://gitlab.gnome.org/GNOME/gdm/-/tags
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.
https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites
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
&legal;
^
/home/repo/gdm-plymouth/src/build/../gdm/docs//C/index.docbook:84: parser error : Entity 'legal' not defined
&legal;
^
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/scannermain.py", line 42, in <module> from giscanner.dumper import compile_introspection_binary File "/usr/lib/gobject-introspection/giscanner/dumper.py", line 33, in <module> from .gdumpparser import IntrospectionBinary File "/usr/lib/gobject-introspection/giscanner/gdumpparser.py", line 35, in <module> from .transformer import TransformerException File "/usr/lib/gobject-introspection/giscanner/transformer.py", line 35, in <module> from .sourcescanner import ( File "/usr/lib/gobject-introspection/giscanner/sourcescanner.py", 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: https://gist.github.com/undu/db2a6a75cb3f17b35bcf232e1a51eeb3
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)
git.gnome.org is GONE! They have moved everything over to GitLab. Please update the tarball to https://gitlab.gnome.org/GNOME/gdm/-/archive/3.28.0/gdm-3.28.0.tar.gz (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 : https://gitlab.gnome.org/GNOME/gdm/-/archive/gnome-3-28/gdm-gnome-3-28.tar.bz2
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. https://github.com/eaceaser/gdm-plymouth 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:
pkgver=3.28.0
pkgrel=0
...
sha256sums=('2908bc2e84bd5c14d0736e58afc31ccdbb05b5314df66093d6d81d631a9811e9'
...)
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.
Pinned Comments
Taijian commented on 2020-08-20 20:48 (UTC) (edited on 2022-03-31 10:53 (UTC) by Taijian)
Attention
It is no longer neccessary or recommended to use
gdm-plymouth.service
in place ofgdm.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!