After upgrading from Fedora 24 to Fedora 25 i found I couldn't login to my home directory. What I could do was login as root. I have a Hewlett-Packard HP Pavilion dv2700 Notebook PC/30CD, BIOS F.2A 03/25/2008
Has anybody had this same problem?
I had this same problem after a fresh install of Fedora (don't remember the release). As root: useradd -u youruserUID -D /your/home/directory youruser passwd youruser newpasswd newpasswd
On 11/23/2016 05:50 AM, jharbold@comcast.net wrote:
After upgrading from Fedora 24 to Fedora 25 i found I couldn't login to my home directory. What I could do was login as root. I have a Hewlett-Packard HP Pavilion dv2700 Notebook PC/30CD, BIOS F.2A 03/25/2008
Has anybody had this same problem? _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Please remember, I did an upgrade, not an install. I checked the permissions of my home directory and they are, "drwxrwxrwx.", and the permissions for /home is "drwxr-xr-x.". The permissions for /root is "r-xr-x---.".
The problem could be one of permissions.
On 11/23/16 12:50, jharbold@comcast.net wrote:
After upgrading from Fedora 24 to Fedora 25 i found I couldn't login to my home directory. What I could do was login as root. I have a Hewlett-Packard HP Pavilion dv2700 Notebook PC/30CD, BIOS F.2A 03/25/2008
After you login as root.
Open a terminal session and try...
su - yourusername
Are you taken to your /home directory?
On Wed, 2016-11-23 at 09:53 -0500, fred roller wrote:
who owns the user account after upgrade?
ls -l /home
Please follow standard practice and quote the relevant part of whatever message you are replying to. Forcing your readers to look for some previous message in the thread in order to understand what you're talking about is not going to win you any friends.
poc
On Wed, Nov 23, 2016 at 02:46:33PM -0000, jharbold@comcast.net wrote:
Yes,after logging in as root, using a terminal, I can login to my home directory.
You might try `restorecon -Rv /home` (as root) to reset SELinux contexts. I don't see why this would have been damaged during an upgrade, but stranger things have happened.
On Wed, 2016-11-23 at 14:46 +0000, jharbold@comcast.net wrote:
Yes,after logging in as root, using a terminal, I can login to my home directory.
Being unable to login as yourself to the graphical user interface (GUI), but able to login to the command line interface, and root being able to log in to the GUI sounds exactly like an old problem I've come across:
The permissions for the /tmp directory may be wrong. If they are, the GUI can't create the files it wants to, in there, as it tries to start up.
If I type this command: ls -ld /tmp I get this result, for a normal /tmp directory: drwxrwxrwt. 19 root root 12288 Nov 24 07:09 /tmp/
Note that all users (owner, group, and others) have read, write, and execute permissions, and that the other user has the sticky bit set (the final "t" in the permissions flags. And it's owned by root:root, the rest of the details are unimportant.
This can happen if you bodge things up while working on the /tmp directory, itself, or fail to mount /tmp onto a tmp directory in the root (and the directory has different permissions), etc.
On 11/22/2016 10:50 PM, jharbold@comcast.net wrote:
After upgrading from Fedora 24 to Fedora 25 i found I couldn't login to my home directory. What I could do was login as root. I have a Hewlett-Packard HP Pavilion dv2700 Notebook PC/30CD, BIOS F.2A 03/25/2008
Has anybody had this same problem? _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I'm not presently a Fedora user, but you should be able to make the /home directory accessible to all:
From root, (or from elsewhere, su and then password,) then: chmod a+x /home and now everyone on the system should be able to access /home.
If you want to limit it, then look up: http://www.gnu.org/software/coreutils/chmod
--doug
I've solved the problem. It has to do with using either Wayland versus Xorg. I search for Gnome bugs relating to logging in and found one that said to edit /etc/gdm/custom.conf. From the script fragment below, uncomment the line below to force the login screen to use Xorg, save and reboot
[daemon] # Uncoment the line below to force the login screen to use Xorg #WaylandEnable=false # JEH WaylandEnable=false
Apparently Wayland does not currently work on an HP Pavilion notebook.
It is good that one can select between Wayland and Xorg.
Consider this thread closed.