[SOLVED] Can't log in using GUI (IceLockAuthFile failed)

XndrK · 2016-10-21 13:51:36

I'm trying to log in to Arch using GNOME 3, but when I try, it just drops me back on the login screen. I tried running journalctl -f on a separate tty window and got this:

Oct 21 08:40:29 daedalus systemd[869]: Started D-Bus User Message Bus.
Oct 21 08:40:29 daedalus gnome-session[896]: gnome-session-binary[896]: WARNING: IceLockAuthFile failed: Permission denied
Oct 21 08:40:29 daedalus gnome-session-binary[896]: WARNING: IceLockAuthFile failed: Permission denied
Oct 21 08:40:29 daedalus gdm-password][865]: pam_unix(gdm-password:session): session closed for user xander
Oct 21 08:40:29 daedalus systmd-logind[337]: Removed session c4.

I tried Googling IceLockAuthFile and unfortunately couldn't find much.

I've recently moved my /home folder to a new partition, if that changes anything.

Thanks for the help.

Edit From the Future: Turns out that I had the permissions on my home folder set up all wacky. Kudos to JohnBobSmith for the answer.

Last edited by XndrK (2016-10-22 19:12:08)

Scimmia · 2016-10-21 13:53:20

What are the permissions on ~/.ICEauthority?

WorMzy · 2016-10-21 13:55:06

How exactly did you move your home folder? What are the permissions on the new partition?

XndrK · 2016-10-21 14:05:00

Scimmia: -rw-------

XndrK · 2016-10-22 01:08:13

Anything?

Scimmia · 2016-10-22 01:28:49

If you want more, start by fully answering the questions asked. You only partially answered mine and ignored WorMzy's.

XndrK · 2016-10-22 02:30:20

Oh, yeah, derp. Forgot that people can't read each other's minds. I'm really bad at that.

I honestly forgot how I moved my /home folder; I did a lot of tutorial following and stuff (involving egregious abuse of mount, if I recall correctly -- which I probably don't). Sorry.

I'm a bit new to Arch, so I don't exactly know what y'all mean by that, but if I run ls -l over /dev/, I get brw-rw---- in the permissions section. I hope that's what y'all wanted.

Also, this "can't access the home folder" thing appears to be going on on all of my programs (including but not limited to Irssi and Emacs), as well as on my Manjaro installation on another partition (they share the /home partition).

Hope this helped a lot more than my last (admittedly dumb) post.

Last edited by XndrK (2016-10-22 02:31:57)

Scimmia · 2016-10-22 02:47:31

Yep, sounds like you screwed up permissions on your home dir. Note that user and group are a critical part of permissions.

XndrK · 2016-10-22 14:52:26

How do I go about fixing that? Do I need to change the permissions on /dev/sda6 itself, or is there something else I'm missing?

Thanks.

seth · 2016-10-22 15:43:36

stat ~/.

XndrK · 2016-10-22 16:40:38

  File:'/home/xander/'
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 806h/2054d      Inode: 1966081     Links: 14
Access: (0775/drwxrwxr-x)  Uid: ( 1005/  xander)   Gid: ( 1005/  xander)
Access: 2016-10-22 09:42:51.019959618 -0500
Modify: 2016-10-22 11:03:02.463202521 -0500
Change: 2016-10-22 11:03:02.463202521 -0500
 Birth: -

seth · 2016-10-22 16:51:05

Assuming "id -u" is 1005, that's fine.
Assuming ~/.ICEauthority is owned by id 1005, that would be ok as well and there should be no permission problem. Try to (re)move the file and log in.

XndrK · 2016-10-22 17:08:13

I can get into GNOME now, but MATE (which runs on X instead of Wayland -- I'm going to assume that has something to do with it) and Firefox (because it wants access to the home folder and can't get it -- quote: "Your Firefox profile cannot be loaded. It may be missing or inaccessible.") are still broken.

So bash can get to my home dir, my editors can get to my home dir, GNOME can get to my home dir, but my applications can't.

Hope this helps.

loqs · 2016-10-22 17:29:48

$ find ~ \( \! -uid `id -u` \) -o \( \! -gid `id -g` \)

This should find all files and directories in the user home directory where the uid is not that of the user or the gid is not that of the user.

JohnBobSmith · 2016-10-22 18:00:59

XndrK wrote:

...
I've recently moved my /home folder to a new partition, if that changes anything.

This changes things quite a bit. As far as I know, the only way to move a partition requires root access. My immediate thoughts are that everything inside your home directory is now owned by root and not your user. Thus when you log in as yourself you cannot access the files because you don't actually own then anymore. Symptoms include a great deal of permission denied errors. Lets make sure this is the case before fixing (breaking) something that didn't need to be broke. Can you paste back the output of the following command here? Remember to use code tags!

 cd; ls -al | grep root

If you see something like the following:

[jbs@dmb-gaming-laptop ~]$ cd; ls -al | grep root
drwxr-xr-x 2 root root   4096 Oct 22 11:55 fakeRootDir
[jbs@dmb-gaming-laptop ~]$

This confirms my suspicion, because "root root" means root is the owner and the group of said file or folder. If you get no output, let us know too because that eliminates a possible reason as to why your files are messed up. This is very fixable, if this (incorrect ownership) is indeed the case.

EDIT: This problem I've just described seems to be what the previous posters were trying to (and may have) solved. So now I feel a bit stupid for being redundant.... But the idea is that, before you go around chomod'ing everything, the simplest of solutions is to ensure you own the files to prevent excessive and/or unnecessary troubleshooting (been there, done that... flash drives are tricky things lol.)

Last edited by JohnBobSmith (2016-10-22 18:12:19)

XndrK · 2016-10-22 18:14:41

drwxr-xr-x  4 root   root   4096 Sep 30  2015 ..

loqs · 2016-10-22 18:33:29

If running firefox from the console does not list the files / directories it can not access then you should be able to find them from the output of

$ strace -e trace=file firefox

JohnBobSmith · 2016-10-22 18:38:27

I want to try something. Be very, very careful with this command. I take no responsibility if this makes things worse. This is a recursive command. The idea is that this sets everything in /home/<username> to be owned by you and your group (usually wheel). This makes sense as its your home directory. With that said, go ahead to try this. Be sure to substitute your username and group!

sudo chown -R <username>:<group> /home/<username>

Your username can be grabbed with the whoami command, the groups you are in can be found with the groups command. The group should be wheel if you are using sudo, unless you set it otherwise.

loqs · 2016-10-22 18:43:16

Then there should have been some output from the command in post #14 should there not? This would avoid using such a command if it serves no purpose.
Also the primary group being wheel instead of a group with the same name as the user or the 'users' group seems strange to me.

JohnBobSmith · 2016-10-22 18:54:00

In my case, I have jbs:wheel for all my files, for reasons I'm not quite sure of to be honest lol... Therefore, it probably is better to use <username>:<username> as you implicitly suggested loqs. Especially if one is concerned about allowing sudo access to files or directories (i'm not as I am the sole user of my device and I wish to have more control over it.). Good catch!

XndrK · 2016-10-22 19:08:24

JohnBobSmith wrote:

I want to try something. Be very, very careful with this command. I take no responsibility if this makes things worse. This is a recursive command. The idea is that this sets everything in /home/<username> to be owned by you and your group (usually wheel). This makes sense as its your home directory. With that said, go ahead to try this. Be sure to substitute your username and group!
sudo chown -R <username>:<group> /home/<username>
Your username can be grabbed with the whoami command, the groups you are in can be found with the groups command. The group should be wheel if you are using sudo, unless you set it otherwise.

Worked.

seth · 2016-10-22 19:15:00

https://bbs.archlinux.org/viewtopic.php … 4#p1663514 implies that you lack execution rights on some dir firefox wants to access a file in, then.
Also in case you should have made everything group:wheel (or users rather than your uid) this implies several security risks and (from another thread in the newbie corner ;-) you'll at some point in a possible future have trouble reg. ssh because of this.

loqs · 2016-10-22 19:35:00

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 4#p1663514 implies that you lack execution rights on some dir firefox wants to access a file in, then.

Did you miss link? putting the command and output together would give

$ cd; ls -al | grep root
drwxr-xr-x  4 root   root   4096 Sep 30  2015 ..

Where .. should be the entry for /home

seth · 2016-10-22 19:43:37

Maybe, I didn't really read all messages inbetween (sorry) and took it for the output of the find command. If that was however empty, my claim about a not accessible directory stands ;-)

XndrK · 2016-10-22 19:56:33

Okay, my laptop works now (and hasn't in some time), but I do care about security risks:

I am in the groups wheel and xander (which I apparently made by accident following some other instructions I found on the webotubes). Setting the home dir's group to xander breaks everything. What should it be, and why? (I never have understood the concept of groups.)

Arch Linux

#1 2016-10-21 13:51:36

[SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#2 2016-10-21 13:53:20

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#3 2016-10-21 13:55:06

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#4 2016-10-21 14:05:00

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#5 2016-10-22 01:08:13

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#6 2016-10-22 01:28:49

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#7 2016-10-22 02:30:20

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#8 2016-10-22 02:47:31

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#9 2016-10-22 14:52:26

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#10 2016-10-22 15:43:36

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#11 2016-10-22 16:40:38

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#12 2016-10-22 16:51:05

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#13 2016-10-22 17:08:13

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#14 2016-10-22 17:29:48

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#15 2016-10-22 18:00:59

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#16 2016-10-22 18:14:41

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#17 2016-10-22 18:33:29

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#18 2016-10-22 18:38:27

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#19 2016-10-22 18:43:16

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#20 2016-10-22 18:54:00

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#21 2016-10-22 19:08:24

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#22 2016-10-22 19:15:00

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#23 2016-10-22 19:35:00

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#24 2016-10-22 19:43:37

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

#25 2016-10-22 19:56:33

Re: [SOLVED] Can't log in using GUI (IceLockAuthFile failed)

Board footer