Authentication Problem on first Loging attempt 18.04
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
When I start my system and try logging in to my user in the first attempt event thought the password is correct the screen goes blank just showing the background and after a long while it shows Authentication Error.
Why is this happening and how do I fix it?
Update 1:
This is all I could dig up from syslogs
Apr 28 15:05:35 akxer-Alienware-15-R3 org.gnome.Shell.desktop[2155]: polkit-agent-helper-1: pam_authenticate failed: Authentication failure
Apr 28 16:26:06 akxer-Alienware-15-R3 systemd[1]: Stopping Authorization Manager...
login login-screen 18.04
asked Apr 28 at 11:01
akabhirav
1,00521029
add a comment |Â
up vote
1
down vote
favorite
When I start my system and try logging in to my user in the first attempt event thought the password is correct the screen goes blank just showing the background and after a long while it shows Authentication Error.
Why is this happening and how do I fix it?
Update 1:
This is all I could dig up from syslogs
Apr 28 15:05:35 akxer-Alienware-15-R3 org.gnome.Shell.desktop[2155]: polkit-agent-helper-1: pam_authenticate failed: Authentication failure
Apr 28 16:26:06 akxer-Alienware-15-R3 systemd[1]: Stopping Authorization Manager...
login login-screen 18.04
asked Apr 28 at 11:01
akabhirav
1,00521029
What is the exact error? It's most likely caused by having run elevated commands that changed files in your personal space. The exact error can make it more certain the culprit.
– L. D. James
Apr 28 at 11:12
The only error I can see is Authentication Error and nothing else, how do I find more information.
– akabhirav
Apr 28 at 11:21
The last update of your question helped. The first suspected culprit maybe unlikely. This gives more to work with.
– L. D. James
Apr 28 at 11:26
Try resetting your password from the console and see if that clears it up. From the console run:password
– L. D. James
Apr 28 at 11:35
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
When I start my system and try logging in to my user in the first attempt event thought the password is correct the screen goes blank just showing the background and after a long while it shows Authentication Error.
Why is this happening and how do I fix it?
Update 1:
This is all I could dig up from syslogs
Apr 28 15:05:35 akxer-Alienware-15-R3 org.gnome.Shell.desktop[2155]: polkit-agent-helper-1: pam_authenticate failed: Authentication failure
Apr 28 16:26:06 akxer-Alienware-15-R3 systemd[1]: Stopping Authorization Manager...
login login-screen 18.04
asked Apr 28 at 11:01
akabhirav
1,00521029
When I start my system and try logging in to my user in the first attempt event thought the password is correct the screen goes blank just showing the background and after a long while it shows Authentication Error.
Why is this happening and how do I fix it?
Update 1:
This is all I could dig up from syslogs
Apr 28 15:05:35 akxer-Alienware-15-R3 org.gnome.Shell.desktop[2155]: polkit-agent-helper-1: pam_authenticate failed: Authentication failure
Apr 28 16:26:06 akxer-Alienware-15-R3 systemd[1]: Stopping Authorization Manager...
login login-screen 18.04
asked Apr 28 at 11:01
akabhirav
1,00521029
edited Apr 28 at 11:21
asked Apr 28 at 11:01
akabhirav
1,00521029
asked Apr 28 at 11:01
akabhirav
1,00521029
asked Apr 28 at 11:01
akabhirav
1,00521029
1,00521029
What is the exact error? It's most likely caused by having run elevated commands that changed files in your personal space. The exact error can make it more certain the culprit.
– L. D. James
Apr 28 at 11:12
The only error I can see is Authentication Error and nothing else, how do I find more information.
– akabhirav
Apr 28 at 11:21
The last update of your question helped. The first suspected culprit maybe unlikely. This gives more to work with.
– L. D. James
Apr 28 at 11:26
Try resetting your password from the console and see if that clears it up. From the console run:password
– L. D. James
Apr 28 at 11:35
add a comment |Â
What is the exact error? It's most likely caused by having run elevated commands that changed files in your personal space. The exact error can make it more certain the culprit.
– L. D. James
Apr 28 at 11:12
The only error I can see is Authentication Error and nothing else, how do I find more information.
– akabhirav
Apr 28 at 11:21
The last update of your question helped. The first suspected culprit maybe unlikely. This gives more to work with.
– L. D. James
Apr 28 at 11:26
Try resetting your password from the console and see if that clears it up. From the console run:password
– L. D. James
Apr 28 at 11:35
What is the exact error? It's most likely caused by having run elevated commands that changed files in your personal space. The exact error can make it more certain the culprit.
– L. D. James
Apr 28 at 11:12
What is the exact error? It's most likely caused by having run elevated commands that changed files in your personal space. The exact error can make it more certain the culprit.
– L. D. James
Apr 28 at 11:12
The only error I can see is Authentication Error and nothing else, how do I find more information.
– akabhirav
Apr 28 at 11:21
The only error I can see is Authentication Error and nothing else, how do I find more information.
– akabhirav
Apr 28 at 11:21
The last update of your question helped. The first suspected culprit maybe unlikely. This gives more to work with.
– L. D. James
Apr 28 at 11:26
The last update of your question helped. The first suspected culprit maybe unlikely. This gives more to work with.
– L. D. James
Apr 28 at 11:26
Try resetting your password from the console and see if that clears it up. From the console run:
password– L. D. James
Apr 28 at 11:35
Try resetting your password from the console and see if that clears it up. From the console run:
password– L. D. James
Apr 28 at 11:35
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
I am experiencing similar - the first login after a reboot works, then after that the above happens. I do notice that the second login screen looks a bit different so I think this is the right track. Uncommenting the WaylandEnable=False line has not worked though unfortunately.
answered May 27 at 4:45
Marshalleq
416
What you wrote is not an answer but a comment to the previous answer. I am warning you about the downvotes to come if you don't move it to the comments
– akabhirav
May 27 at 7:59
add a comment |Â
up vote
0
down vote
I had this issue on Ubuntu 18.04 too. I solved it by uncommenting WaylandEnable=false in /etc/gdm3/custom.conf (forcing GDM to run under X11).
answered May 4 at 22:12
user825996
1
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I am experiencing similar - the first login after a reboot works, then after that the above happens. I do notice that the second login screen looks a bit different so I think this is the right track. Uncommenting the WaylandEnable=False line has not worked though unfortunately.
answered May 27 at 4:45
Marshalleq
416
What you wrote is not an answer but a comment to the previous answer. I am warning you about the downvotes to come if you don't move it to the comments
– akabhirav
May 27 at 7:59
add a comment |Â
up vote
1
down vote
I am experiencing similar - the first login after a reboot works, then after that the above happens. I do notice that the second login screen looks a bit different so I think this is the right track. Uncommenting the WaylandEnable=False line has not worked though unfortunately.
answered May 27 at 4:45
Marshalleq
416
What you wrote is not an answer but a comment to the previous answer. I am warning you about the downvotes to come if you don't move it to the comments
– akabhirav
May 27 at 7:59
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I am experiencing similar - the first login after a reboot works, then after that the above happens. I do notice that the second login screen looks a bit different so I think this is the right track. Uncommenting the WaylandEnable=False line has not worked though unfortunately.
answered May 27 at 4:45
Marshalleq
416
I am experiencing similar - the first login after a reboot works, then after that the above happens. I do notice that the second login screen looks a bit different so I think this is the right track. Uncommenting the WaylandEnable=False line has not worked though unfortunately.
answered May 27 at 4:45
Marshalleq
416
answered May 27 at 4:45
Marshalleq
416
answered May 27 at 4:45
Marshalleq
416
answered May 27 at 4:45
Marshalleq
416
416
What you wrote is not an answer but a comment to the previous answer. I am warning you about the downvotes to come if you don't move it to the comments
– akabhirav
May 27 at 7:59
add a comment |Â
What you wrote is not an answer but a comment to the previous answer. I am warning you about the downvotes to come if you don't move it to the comments
– akabhirav
May 27 at 7:59
What you wrote is not an answer but a comment to the previous answer. I am warning you about the downvotes to come if you don't move it to the comments
– akabhirav
May 27 at 7:59
What you wrote is not an answer but a comment to the previous answer. I am warning you about the downvotes to come if you don't move it to the comments
– akabhirav
May 27 at 7:59
add a comment |Â
up vote
0
down vote
I had this issue on Ubuntu 18.04 too. I solved it by uncommenting WaylandEnable=false in /etc/gdm3/custom.conf (forcing GDM to run under X11).
answered May 4 at 22:12
user825996
1
add a comment |Â
up vote
0
down vote
I had this issue on Ubuntu 18.04 too. I solved it by uncommenting WaylandEnable=false in /etc/gdm3/custom.conf (forcing GDM to run under X11).
answered May 4 at 22:12
user825996
1
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I had this issue on Ubuntu 18.04 too. I solved it by uncommenting WaylandEnable=false in /etc/gdm3/custom.conf (forcing GDM to run under X11).
answered May 4 at 22:12
user825996
1
I had this issue on Ubuntu 18.04 too. I solved it by uncommenting WaylandEnable=false in /etc/gdm3/custom.conf (forcing GDM to run under X11).
answered May 4 at 22:12
user825996
1
answered May 4 at 22:12
user825996
1
answered May 4 at 22:12
user825996
1
answered May 4 at 22:12
user825996
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1029172%2fauthentication-problem-on-first-loging-attempt-18-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
What is the exact error? It's most likely caused by having run elevated commands that changed files in your personal space. The exact error can make it more certain the culprit.
– L. D. James
Apr 28 at 11:12
The only error I can see is Authentication Error and nothing else, how do I find more information.
– akabhirav
Apr 28 at 11:21
The last update of your question helped. The first suspected culprit maybe unlikely. This gives more to work with.
– L. D. James
Apr 28 at 11:26
Try resetting your password from the console and see if that clears it up. From the console run:
password– L. D. James
Apr 28 at 11:35