You are not logged in.
I am using plymouth-legacy from the AUR.
When I boot, the plymouth password prompt for my encrypted root partition comes up and I can enter the password. The next screen is the boot splash screen with the "spinfinity" spinning wheel. The screen flickers a few times but never goes away. Pressing escape shows the console that states the plymouth-quit-wait service failed. I can get to tty2 by pressing [Alt][F2] and login there. I think the plymouth-quit-wait service is actually working fine, but the problem is either gdm is failing or plymouth-quit is not running and plymouth-quit-wait times out waiting for something to happen. I am not really sure what the problem could be because it looks like (from the log below) that gdm has a problem with my graphics card, but it has no problem if plymouth isn't running.
Log snippet for plymouth-quit-wait service. (Full log pastebin below).
Sep 07 13:34:48 chrutabaga systemd[1]: plymouth-quit-wait.service start operation timed out. Terminating.
Sep 07 13:34:48 chrutabaga systemd[1]: Failed to start Wait for Plymouth Boot Screen to Quit.
-- Subject: Unit plymouth-quit-wait.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plymouth-quit-wait.service has failed.
--
-- The result is failed.
Sep 07 13:34:48 chrutabaga systemd[1]: Unit plymouth-quit-wait.service entered failed state.
Log snippet for gdm failing. (Full log pastebin below).
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13].
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) intel(0): Failed to claim DRM device.
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Backtrace:
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x593966]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 1: /usr/bin/Xorg.bin (0x400000+0x197b69) [0x597b69]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 2: /usr/lib/libc.so.6 (0x7faf3b2d8000+0x33df0) [0x7faf3b30bdf0]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7faf36524000+0x6f320) [0x7faf36593320]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 4: /usr/bin/Xorg.bin (xf86DeleteScreen+0x5a) [0x480c3a]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 5: /usr/bin/Xorg.bin (InitOutput+0xaf7) [0x47a2b7]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 6: /usr/bin/Xorg.bin (0x400000+0x3b67a) [0x43b67a]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 7: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7faf3b2f8000]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 8: /usr/bin/Xorg.bin (0x400000+0x25d0e) [0x425d0e]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Segmentation fault at address 0x7faf366fa7a6
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: Fatal server error:
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: Please consult the The X.Org Foundation support
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: at http://wiki.x.org
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: for help.
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Please also check the log file at "/dev/null" for additional information.
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Server terminated with error (1). Closing log file.
mkinitcpio.conf
MODULES="i915"
BINARIES=""
FILES=""
HOOKS="base udev plymouth autodetect mdadm_udev lvm2 plymouth-encrypt modconf block filesystems keyboard"
Full log pastebin.
Things I have tried:
Switch to tty2, log in and restart services as below in that order. This brings up gdm, and I can log in without any issue.
sudo systemctl start plymouth-quit
sudo systemctl restart plymouth-quit-wait
sudo systemctl restart gdm-plymouth
Use SLIM as a display manager. This works for some reason, but I don't want to use slim. (Off topic, but I use more than one desktop manager and slim doesn't do a great job with remembering my last session.)
Don't use a display manager. Plymouth boots fine to a console. There are no errors. I can then start gdm with no problem.
sudo systemctl start gdm
Using lightdm has the same result as gdm.
Using the gdm.service instead of gdm-plymouth.service has the same result.
I tried this thread. I don't have an nvidia card and the modified gdm-plymouth service didn't change anything.
I also followed this thread on the fedora forums, which advised moving /var/journal to /var/journal.org. That seems pretty bizarre but I tried it anyways. No effect for me.
Last edited by jkav77 (2014-09-08 23:30:00)
Offline
This is strange, I'm using GDM with Plymouth 0.8.8-7 from a now deleted package "plymouth-release" and I have no issues.
I'm using gdm rather than gdm-plymouth. Also be sure to run mkinitcpio every time you change themes.
If you wish, I can give you a package of the version I have if you wish to try it. (link)
Last edited by markzz (2015-09-28 19:07:48)
I don't want to work. I want to bang on the drum all day.
Offline
@markzz, Thanks! For some reason, the package you posted works for me. I didn't do anything different than remove plymouth-legacy and install the package you posted. Interestingly, the version you have is not available on the freedesktop.org plymouth source site. The one there and in plymouth-legacy from the AUR is 0.8.8-1. For whatever reason, this is the solution for me.
Offline
@markzz, Thanks! For some reason, the package you posted works for me. I didn't do anything different than remove plymouth-legacy and install the package you posted. Interestingly, the version you have is not available on the freedesktop.org plymouth source site. The one there and in plymouth-legacy from the AUR is 0.8.8-1. For whatever reason, this is the solution for me.
I'm glad I could help!
I don't want to work. I want to bang on the drum all day.
Offline
I am the maintainer for the plymouth-legacy. I'll look into figuring out something. I don't use GDM though.
Offline
I am the maintainer for the plymouth-legacy. I'll look into figuring out something. I don't use GDM though.
Doesn't matter if you don't use it, the package includes parts for GDM. Some testing for KDM or other login managers would be a good thing to do too.
Last edited by markzz (2014-09-09 03:15:48)
I don't want to work. I want to bang on the drum all day.
Offline
flamusdiu wrote:I am the maintainer for the plymouth-legacy. I'll look into figuring out something. I don't use GDM though.
Doesn't matter if you don't use it, the package includes parts for GDM. Some testing for KDM or other login managers would be a good thing to do too.
I am aware of that. I don't have other login mangers installed but something changed between the two updates. As I said, I'll look into it. I know SLiM and LightDM work with this build. Let you know something soon.
Offline
Changed or modified files between the two:
etc/plymouth/plymouthd.conf
usr/lib/initcpio/hooks/plymouth
usr/lib/initcpio/hooks/plymouth-encrypt
usr/lib/initcpio/install/plymouth
usr/lib/plymouth/plymouth-populate-initrd
usr/lib/plymouth/plymouth-update-initrd
lib/
Offline