GNOME Bugzilla – Bug 740802
gdm package inconsistent regarding conflict with plymouth-quit.service
Last modified: 2014-12-19 14:05:34 UTC
When gdm is compiled without "--with-plymouth" option, gdm.service should not conflict with plymouth-quit.service otherwise plymouth-quit service will not run and neither will gdm ask plymouth to quit. Is it better to have --with-plymouth as the default for compiling gdm? Otherwise the conflict declaration in gdm.service should be tied to that same option.
Created attachment 292209 [details] [review] configure: require plymouth if using systemd This is only a build requirement since gdm doesn't link against plymouth or anything like that and will work if it's not installed when run.
Attachment 292209 [details] pushed as f8a21cd - configure: require plymouth if using systemd
so my fix actually breaks some distros that don't ship plymouth but do ship systemd, reopening.
Created attachment 293055 [details] [review] Revert "configure: require plymouth if using systemd" This reverts commit f8a21cd6cb2095e80889df8c41036e2df31ba01a.
Created attachment 293056 [details] [review] configure: require --without-plymouth to disable plymouth support Plymouth is used pretty widely these days, and we're getting bugs from people who didn't have the buildrequires, didn't get plymouth support and were left with a broken setup. Instead, just just let the distros that don't use plymouth opt out.
Created attachment 293057 [details] [review] systemd: strip plymouth bits from unit file if built --without-plymouth Otherwise, if you have plymouth, but build --without-plymouth then boot will screw up
Attachment 293055 [details] pushed as a3ebb3e - Revert "configure: require plymouth if using systemd" Attachment 293056 [details] pushed as 0950c62 - configure: require --without-plymouth to disable plymouth support Attachment 293057 [details] pushed as 68259e0 - systemd: strip plymouth bits from unit file if built --without-plymouth