Finally found the solutions: 1. rpm --verify indicated that there were still some ownership issues. I reinstalled gdm and a couple of other packages to correct some of them 2. 'journalctl --system' also displayed a few issues that rpm did not expose. System now boots up into graphical.target.
On Tue, May 17, 2016 at 11:34 AM, Jerry Feldman <[email protected]> wrote: > I somehow messed up one of my Fedora 23 systems where all the setuid bits > got cleared. I have since fixed just about all of them. But, the one issue > remains is that I can't boot into the graphical.target (formerly run level > 5). I have since set the default target to multiuser.target (formerly run > level 3). I then log in and startx. I'm sure I missed setting a setuid bit > somewhere. > > -- > -- > Jerry Feldman <[email protected]> > Boston Linux and Unix > PGP key id: B7F14F2F > Key fingerprint: D937 A424 4836 E052 2E1B 8DC6 24D7 000F B7F1 4F2F > -- -- Jerry Feldman <[email protected]> Boston Linux and Unix PGP key id: B7F14F2F Key fingerprint: D937 A424 4836 E052 2E1B 8DC6 24D7 000F B7F1 4F2F _______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
