Cannot login into GNOME, kicking me back to login screen
up vote
1
down vote
favorite
I am not able to login into GNOME desktop, it happened yesterday after upgrade.
In login screen, if I enter my password and press ENTER I am getting login screen again.
System details:
- linux 4.4.5-1
- gnome-shell 3.20.0-3
- gnome-desktop 1:3.20.1-1
- gnome-session 3.20.1-1
- gdm 3.20.0-1
Logs:
- Xorg log: http://sprunge.us/SHSh
- Journalctl log: http://sprunge.us/GIaM
Few tips for you to help me:
- I am able to login in GNOME Wayland session but not with default GNOME (with xorg)
- I created new user (from console) but same problem occurs when this new user tries to login.
- output of uname -a:
Linux ArchLinux 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux
Please ask if you need more info.
gnome3
asked Apr 13 '16 at 11:06
Edward Torvalds
2,44933260
add a comment |
up vote
1
down vote
favorite
I am not able to login into GNOME desktop, it happened yesterday after upgrade.
In login screen, if I enter my password and press ENTER I am getting login screen again.
System details:
- linux 4.4.5-1
- gnome-shell 3.20.0-3
- gnome-desktop 1:3.20.1-1
- gnome-session 3.20.1-1
- gdm 3.20.0-1
Logs:
- Xorg log: http://sprunge.us/SHSh
- Journalctl log: http://sprunge.us/GIaM
Few tips for you to help me:
- I am able to login in GNOME Wayland session but not with default GNOME (with xorg)
- I created new user (from console) but same problem occurs when this new user tries to login.
- output of uname -a:
Linux ArchLinux 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux
Please ask if you need more info.
gnome3
asked Apr 13 '16 at 11:06
Edward Torvalds
2,44933260
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am not able to login into GNOME desktop, it happened yesterday after upgrade.
In login screen, if I enter my password and press ENTER I am getting login screen again.
System details:
- linux 4.4.5-1
- gnome-shell 3.20.0-3
- gnome-desktop 1:3.20.1-1
- gnome-session 3.20.1-1
- gdm 3.20.0-1
Logs:
- Xorg log: http://sprunge.us/SHSh
- Journalctl log: http://sprunge.us/GIaM
Few tips for you to help me:
- I am able to login in GNOME Wayland session but not with default GNOME (with xorg)
- I created new user (from console) but same problem occurs when this new user tries to login.
- output of uname -a:
Linux ArchLinux 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux
Please ask if you need more info.
gnome3
asked Apr 13 '16 at 11:06
Edward Torvalds
2,44933260
I am not able to login into GNOME desktop, it happened yesterday after upgrade.
In login screen, if I enter my password and press ENTER I am getting login screen again.
System details:
- linux 4.4.5-1
- gnome-shell 3.20.0-3
- gnome-desktop 1:3.20.1-1
- gnome-session 3.20.1-1
- gdm 3.20.0-1
Logs:
- Xorg log: http://sprunge.us/SHSh
- Journalctl log: http://sprunge.us/GIaM
Few tips for you to help me:
- I am able to login in GNOME Wayland session but not with default GNOME (with xorg)
- I created new user (from console) but same problem occurs when this new user tries to login.
- output of uname -a:
Linux ArchLinux 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux
Please ask if you need more info.
gnome3
gnome3
asked Apr 13 '16 at 11:06
Edward Torvalds
2,44933260
asked Apr 13 '16 at 11:06
Edward Torvalds
2,44933260
asked Apr 13 '16 at 11:06
Edward Torvalds
2,44933260
asked Apr 13 '16 at 11:06
Edward Torvalds
2,44933260
asked Apr 13 '16 at 11:06
Edward Torvalds
2,44933260
2,44933260
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
up vote
1
down vote
accepted
I guess the reason is
/etc/profile.d/bundler-exec.sh: line 12: `bundler-installed': not a valid identifier
in journalctl.log
Can you provide this file?
answered Apr 13 '16 at 12:02
Sild
235110
here is the scriptbundler-exec.sh( sprunge.us/BKii ). can you please show what is wrong with it?
– Edward Torvalds
Apr 13 '16 at 12:20
I don't familiar with ruby enough, so You can try to comment out all rows in this file to check the error will disappear.
– Sild
Apr 13 '16 at 12:44
moving that file to some other location solves my problem ;-). thanks
– Edward Torvalds
Apr 13 '16 at 12:57
add a comment |
up vote
1
down vote
I had this problem too. It was solved when I deleted my ~/.ICEAuthority file and allowed it to be recreated.
answered Aug 23 '17 at 0:23
Thomas Profitt
111
add a comment |
up vote
0
down vote
I had this problem and it turned out to be one of my Gnome Shell extensions, but I'm still not sure which one.
To check if this is your problem, open the Gnome Shell Extensions application (it will run in Cinnamon on Fedora and I'd bet other desktop environments). There is a "master" on/off switch that you can switch to Off and it will keep your existing on/off selections for the extensions. Then you can log in and see if you get kicked back.
My next step was to turn on the master switch and then turn off any extension that I didn't REALLY want, or that I'd recently enabled. I must've turned off the right one, because my logins are working fine now.
A few things that might indicate whether this is the cause of the problem for you:
1) Gnome 3 on Wayland and Xorg both kick you back to the login screen
2) Logging in with the Cinnamon or another desktop works fine.
I was never able to find a log that clearly indicated the problem, so if someone knows, that would be a nice addition to this thread.
answered Dec 2 at 6:01
ahaning
1
New contributor
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I guess the reason is
/etc/profile.d/bundler-exec.sh: line 12: `bundler-installed': not a valid identifier
in journalctl.log
Can you provide this file?
answered Apr 13 '16 at 12:02
Sild
235110
here is the scriptbundler-exec.sh( sprunge.us/BKii ). can you please show what is wrong with it?
– Edward Torvalds
Apr 13 '16 at 12:20
I don't familiar with ruby enough, so You can try to comment out all rows in this file to check the error will disappear.
– Sild
Apr 13 '16 at 12:44
moving that file to some other location solves my problem ;-). thanks
– Edward Torvalds
Apr 13 '16 at 12:57
add a comment |
up vote
1
down vote
accepted
I guess the reason is
/etc/profile.d/bundler-exec.sh: line 12: `bundler-installed': not a valid identifier
in journalctl.log
Can you provide this file?
answered Apr 13 '16 at 12:02
Sild
235110
here is the scriptbundler-exec.sh( sprunge.us/BKii ). can you please show what is wrong with it?
– Edward Torvalds
Apr 13 '16 at 12:20
I don't familiar with ruby enough, so You can try to comment out all rows in this file to check the error will disappear.
– Sild
Apr 13 '16 at 12:44
moving that file to some other location solves my problem ;-). thanks
– Edward Torvalds
Apr 13 '16 at 12:57
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I guess the reason is
/etc/profile.d/bundler-exec.sh: line 12: `bundler-installed': not a valid identifier
in journalctl.log
Can you provide this file?
answered Apr 13 '16 at 12:02
Sild
235110
I guess the reason is
/etc/profile.d/bundler-exec.sh: line 12: `bundler-installed': not a valid identifier
in journalctl.log
Can you provide this file?
answered Apr 13 '16 at 12:02
Sild
235110
answered Apr 13 '16 at 12:02
Sild
235110
answered Apr 13 '16 at 12:02
Sild
235110
answered Apr 13 '16 at 12:02
Sild
235110
235110
here is the scriptbundler-exec.sh( sprunge.us/BKii ). can you please show what is wrong with it?
– Edward Torvalds
Apr 13 '16 at 12:20
I don't familiar with ruby enough, so You can try to comment out all rows in this file to check the error will disappear.
– Sild
Apr 13 '16 at 12:44
moving that file to some other location solves my problem ;-). thanks
– Edward Torvalds
Apr 13 '16 at 12:57
add a comment |
here is the scriptbundler-exec.sh( sprunge.us/BKii ). can you please show what is wrong with it?
– Edward Torvalds
Apr 13 '16 at 12:20
I don't familiar with ruby enough, so You can try to comment out all rows in this file to check the error will disappear.
– Sild
Apr 13 '16 at 12:44
moving that file to some other location solves my problem ;-). thanks
– Edward Torvalds
Apr 13 '16 at 12:57
here is the script
bundler-exec.sh ( sprunge.us/BKii ). can you please show what is wrong with it?– Edward Torvalds
Apr 13 '16 at 12:20
here is the script
bundler-exec.sh ( sprunge.us/BKii ). can you please show what is wrong with it?– Edward Torvalds
Apr 13 '16 at 12:20
I don't familiar with ruby enough, so You can try to comment out all rows in this file to check the error will disappear.
– Sild
Apr 13 '16 at 12:44
I don't familiar with ruby enough, so You can try to comment out all rows in this file to check the error will disappear.
– Sild
Apr 13 '16 at 12:44
moving that file to some other location solves my problem ;-). thanks
– Edward Torvalds
Apr 13 '16 at 12:57
moving that file to some other location solves my problem ;-). thanks
– Edward Torvalds
Apr 13 '16 at 12:57
add a comment |
up vote
1
down vote
I had this problem too. It was solved when I deleted my ~/.ICEAuthority file and allowed it to be recreated.
answered Aug 23 '17 at 0:23
Thomas Profitt
111
add a comment |
up vote
1
down vote
I had this problem too. It was solved when I deleted my ~/.ICEAuthority file and allowed it to be recreated.
answered Aug 23 '17 at 0:23
Thomas Profitt
111
add a comment |
up vote
1
down vote
up vote
1
down vote
I had this problem too. It was solved when I deleted my ~/.ICEAuthority file and allowed it to be recreated.
answered Aug 23 '17 at 0:23
Thomas Profitt
111
I had this problem too. It was solved when I deleted my ~/.ICEAuthority file and allowed it to be recreated.
answered Aug 23 '17 at 0:23
Thomas Profitt
111
answered Aug 23 '17 at 0:23
Thomas Profitt
111
answered Aug 23 '17 at 0:23
Thomas Profitt
111
answered Aug 23 '17 at 0:23
Thomas Profitt
111
111
add a comment |
add a comment |
up vote
0
down vote
I had this problem and it turned out to be one of my Gnome Shell extensions, but I'm still not sure which one.
To check if this is your problem, open the Gnome Shell Extensions application (it will run in Cinnamon on Fedora and I'd bet other desktop environments). There is a "master" on/off switch that you can switch to Off and it will keep your existing on/off selections for the extensions. Then you can log in and see if you get kicked back.
My next step was to turn on the master switch and then turn off any extension that I didn't REALLY want, or that I'd recently enabled. I must've turned off the right one, because my logins are working fine now.
A few things that might indicate whether this is the cause of the problem for you:
1) Gnome 3 on Wayland and Xorg both kick you back to the login screen
2) Logging in with the Cinnamon or another desktop works fine.
I was never able to find a log that clearly indicated the problem, so if someone knows, that would be a nice addition to this thread.
answered Dec 2 at 6:01
ahaning
1
New contributor
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
I had this problem and it turned out to be one of my Gnome Shell extensions, but I'm still not sure which one.
To check if this is your problem, open the Gnome Shell Extensions application (it will run in Cinnamon on Fedora and I'd bet other desktop environments). There is a "master" on/off switch that you can switch to Off and it will keep your existing on/off selections for the extensions. Then you can log in and see if you get kicked back.
My next step was to turn on the master switch and then turn off any extension that I didn't REALLY want, or that I'd recently enabled. I must've turned off the right one, because my logins are working fine now.
A few things that might indicate whether this is the cause of the problem for you:
1) Gnome 3 on Wayland and Xorg both kick you back to the login screen
2) Logging in with the Cinnamon or another desktop works fine.
I was never able to find a log that clearly indicated the problem, so if someone knows, that would be a nice addition to this thread.
answered Dec 2 at 6:01
ahaning
1
New contributor
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
I had this problem and it turned out to be one of my Gnome Shell extensions, but I'm still not sure which one.
To check if this is your problem, open the Gnome Shell Extensions application (it will run in Cinnamon on Fedora and I'd bet other desktop environments). There is a "master" on/off switch that you can switch to Off and it will keep your existing on/off selections for the extensions. Then you can log in and see if you get kicked back.
My next step was to turn on the master switch and then turn off any extension that I didn't REALLY want, or that I'd recently enabled. I must've turned off the right one, because my logins are working fine now.
A few things that might indicate whether this is the cause of the problem for you:
1) Gnome 3 on Wayland and Xorg both kick you back to the login screen
2) Logging in with the Cinnamon or another desktop works fine.
I was never able to find a log that clearly indicated the problem, so if someone knows, that would be a nice addition to this thread.
answered Dec 2 at 6:01
ahaning
1
New contributor
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had this problem and it turned out to be one of my Gnome Shell extensions, but I'm still not sure which one.
To check if this is your problem, open the Gnome Shell Extensions application (it will run in Cinnamon on Fedora and I'd bet other desktop environments). There is a "master" on/off switch that you can switch to Off and it will keep your existing on/off selections for the extensions. Then you can log in and see if you get kicked back.
My next step was to turn on the master switch and then turn off any extension that I didn't REALLY want, or that I'd recently enabled. I must've turned off the right one, because my logins are working fine now.
A few things that might indicate whether this is the cause of the problem for you:
1) Gnome 3 on Wayland and Xorg both kick you back to the login screen
2) Logging in with the Cinnamon or another desktop works fine.
I was never able to find a log that clearly indicated the problem, so if someone knows, that would be a nice addition to this thread.
answered Dec 2 at 6:01
ahaning
1
New contributor
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 2 at 6:01
ahaning
1
New contributor
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 2 at 6:01
ahaning
1
answered Dec 2 at 6:01
ahaning
1
1
New contributor
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
ahaning is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f276148%2fcannot-login-into-gnome-kicking-me-back-to-login-screen%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
