Login screen reappears after login
I am on Fedora 16 KDE spin. Yesterday I ran the fsck command and that broke things. I can login via the tty, so I guess it has nothing to do with the shadow file. The login screen reappears after login no matter how many times I try to get past it. The permissions are the same as before. Also I have tried renaming the .kde folder. Doesn't help. This affects all the users, even root. My guess is the X server is restarting after login bringing me back to the login screen. Any way I can solve this?
kde
asked Nov 8 '12 at 8:41
Phani KumarPhani Kumar
1435
add a comment |
I am on Fedora 16 KDE spin. Yesterday I ran the fsck command and that broke things. I can login via the tty, so I guess it has nothing to do with the shadow file. The login screen reappears after login no matter how many times I try to get past it. The permissions are the same as before. Also I have tried renaming the .kde folder. Doesn't help. This affects all the users, even root. My guess is the X server is restarting after login bringing me back to the login screen. Any way I can solve this?
kde
asked Nov 8 '12 at 8:41
Phani KumarPhani Kumar
1435
1
I think you should start by looking at~/.xsession-errorsand/var/log/messages
– Joseph R.
Nov 8 '12 at 9:18
also/var/log/Xorg.1.log
– xenoterracide
Nov 8 '12 at 16:25
Can you log in if you dosingleuser mode? If you can't then your/etc/shadowfile might be borked.
– sparticvs
Nov 8 '12 at 18:17
You can also try to start X from sommand line withstartxoptionally redirecting its stdout and stderr:startx 2>startx.err 1>startx.log
– peterph
Nov 8 '12 at 20:17
sorry for the late reply. It was the X server indeed. I followed what peterph said and the startx.err file had this,/usr/bin/ssh-agent: error while loading shared libraries: libfipscheck.so.1: cannot open shared object file: No such file or directory. xinit: connection to X server lost.I have no idea what that means. I tried disabling ssh but it doesn't help.
– Phani Kumar
Nov 9 '12 at 9:35
add a comment |
I am on Fedora 16 KDE spin. Yesterday I ran the fsck command and that broke things. I can login via the tty, so I guess it has nothing to do with the shadow file. The login screen reappears after login no matter how many times I try to get past it. The permissions are the same as before. Also I have tried renaming the .kde folder. Doesn't help. This affects all the users, even root. My guess is the X server is restarting after login bringing me back to the login screen. Any way I can solve this?
kde
asked Nov 8 '12 at 8:41
Phani KumarPhani Kumar
1435
I am on Fedora 16 KDE spin. Yesterday I ran the fsck command and that broke things. I can login via the tty, so I guess it has nothing to do with the shadow file. The login screen reappears after login no matter how many times I try to get past it. The permissions are the same as before. Also I have tried renaming the .kde folder. Doesn't help. This affects all the users, even root. My guess is the X server is restarting after login bringing me back to the login screen. Any way I can solve this?
kde
kde
asked Nov 8 '12 at 8:41
Phani KumarPhani Kumar
1435
asked Nov 8 '12 at 8:41
Phani KumarPhani Kumar
1435
asked Nov 8 '12 at 8:41
Phani KumarPhani Kumar
1435
asked Nov 8 '12 at 8:41
Phani KumarPhani Kumar
1435
asked Nov 8 '12 at 8:41
Phani KumarPhani Kumar
1435
1435
1
I think you should start by looking at~/.xsession-errorsand/var/log/messages
– Joseph R.
Nov 8 '12 at 9:18
also/var/log/Xorg.1.log
– xenoterracide
Nov 8 '12 at 16:25
Can you log in if you dosingleuser mode? If you can't then your/etc/shadowfile might be borked.
– sparticvs
Nov 8 '12 at 18:17
You can also try to start X from sommand line withstartxoptionally redirecting its stdout and stderr:startx 2>startx.err 1>startx.log
– peterph
Nov 8 '12 at 20:17
sorry for the late reply. It was the X server indeed. I followed what peterph said and the startx.err file had this,/usr/bin/ssh-agent: error while loading shared libraries: libfipscheck.so.1: cannot open shared object file: No such file or directory. xinit: connection to X server lost.I have no idea what that means. I tried disabling ssh but it doesn't help.
– Phani Kumar
Nov 9 '12 at 9:35
add a comment |
1
I think you should start by looking at~/.xsession-errorsand/var/log/messages
– Joseph R.
Nov 8 '12 at 9:18
also/var/log/Xorg.1.log
– xenoterracide
Nov 8 '12 at 16:25
Can you log in if you dosingleuser mode? If you can't then your/etc/shadowfile might be borked.
– sparticvs
Nov 8 '12 at 18:17
You can also try to start X from sommand line withstartxoptionally redirecting its stdout and stderr:startx 2>startx.err 1>startx.log
– peterph
Nov 8 '12 at 20:17
sorry for the late reply. It was the X server indeed. I followed what peterph said and the startx.err file had this,/usr/bin/ssh-agent: error while loading shared libraries: libfipscheck.so.1: cannot open shared object file: No such file or directory. xinit: connection to X server lost.I have no idea what that means. I tried disabling ssh but it doesn't help.
– Phani Kumar
Nov 9 '12 at 9:35
1
1
I think you should start by looking at
~/.xsession-errors and /var/log/messages– Joseph R.
Nov 8 '12 at 9:18
I think you should start by looking at
~/.xsession-errors and /var/log/messages– Joseph R.
Nov 8 '12 at 9:18
also
/var/log/Xorg.1.log– xenoterracide
Nov 8 '12 at 16:25
also
/var/log/Xorg.1.log– xenoterracide
Nov 8 '12 at 16:25
Can you log in if you do
single user mode? If you can't then your /etc/shadow file might be borked.– sparticvs
Nov 8 '12 at 18:17
Can you log in if you do
single user mode? If you can't then your /etc/shadow file might be borked.– sparticvs
Nov 8 '12 at 18:17
You can also try to start X from sommand line with
startx optionally redirecting its stdout and stderr: startx 2>startx.err 1>startx.log– peterph
Nov 8 '12 at 20:17
You can also try to start X from sommand line with
startx optionally redirecting its stdout and stderr: startx 2>startx.err 1>startx.log– peterph
Nov 8 '12 at 20:17
sorry for the late reply. It was the X server indeed. I followed what peterph said and the startx.err file had this,
/usr/bin/ssh-agent: error while loading shared libraries: libfipscheck.so.1: cannot open shared object file: No such file or directory. xinit: connection to X server lost. I have no idea what that means. I tried disabling ssh but it doesn't help.– Phani Kumar
Nov 9 '12 at 9:35
sorry for the late reply. It was the X server indeed. I followed what peterph said and the startx.err file had this,
/usr/bin/ssh-agent: error while loading shared libraries: libfipscheck.so.1: cannot open shared object file: No such file or directory. xinit: connection to X server lost. I have no idea what that means. I tried disabling ssh but it doesn't help.– Phani Kumar
Nov 9 '12 at 9:35
add a comment |
2 Answers
2
active
oldest
votes
Given your answers in the comments, the problem is that the program "ssh-agent" can't load the library libfipscheck which it needs in order to run. The quick fix is to edit your .xinitrc file and comment out the call to ssh-agent from it. The real fix is to re-install the package fipscheck-lib .
answered Nov 9 '12 at 11:00
Jenny DJenny D
10.5k22746
Amazing! That did the trick. It was the/etc/X11/xinit/xinitrc-commonfile that had the SSH-AGENT line.
– Phani Kumar
Nov 9 '12 at 15:00
add a comment |
Had same unrecognized login problem with KDE fedora 27-29, and Jenny D's real fix (dnf reinstall fipscheck-lib) solved the problem. Many thanks Jenny D
answered 17 mins ago
Martin LeeMartin Lee
11
New contributor
Martin Lee 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 |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f55176%2flogin-screen-reappears-after-login%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Given your answers in the comments, the problem is that the program "ssh-agent" can't load the library libfipscheck which it needs in order to run. The quick fix is to edit your .xinitrc file and comment out the call to ssh-agent from it. The real fix is to re-install the package fipscheck-lib .
answered Nov 9 '12 at 11:00
Jenny DJenny D
10.5k22746
Amazing! That did the trick. It was the/etc/X11/xinit/xinitrc-commonfile that had the SSH-AGENT line.
– Phani Kumar
Nov 9 '12 at 15:00
add a comment |
Given your answers in the comments, the problem is that the program "ssh-agent" can't load the library libfipscheck which it needs in order to run. The quick fix is to edit your .xinitrc file and comment out the call to ssh-agent from it. The real fix is to re-install the package fipscheck-lib .
answered Nov 9 '12 at 11:00
Jenny DJenny D
10.5k22746
Amazing! That did the trick. It was the/etc/X11/xinit/xinitrc-commonfile that had the SSH-AGENT line.
– Phani Kumar
Nov 9 '12 at 15:00
add a comment |
Given your answers in the comments, the problem is that the program "ssh-agent" can't load the library libfipscheck which it needs in order to run. The quick fix is to edit your .xinitrc file and comment out the call to ssh-agent from it. The real fix is to re-install the package fipscheck-lib .
answered Nov 9 '12 at 11:00
Jenny DJenny D
10.5k22746
Given your answers in the comments, the problem is that the program "ssh-agent" can't load the library libfipscheck which it needs in order to run. The quick fix is to edit your .xinitrc file and comment out the call to ssh-agent from it. The real fix is to re-install the package fipscheck-lib .
answered Nov 9 '12 at 11:00
Jenny DJenny D
10.5k22746
answered Nov 9 '12 at 11:00
Jenny DJenny D
10.5k22746
answered Nov 9 '12 at 11:00
Jenny DJenny D
10.5k22746
answered Nov 9 '12 at 11:00
Jenny DJenny D
10.5k22746
10.5k22746
Amazing! That did the trick. It was the/etc/X11/xinit/xinitrc-commonfile that had the SSH-AGENT line.
– Phani Kumar
Nov 9 '12 at 15:00
add a comment |
Amazing! That did the trick. It was the/etc/X11/xinit/xinitrc-commonfile that had the SSH-AGENT line.
– Phani Kumar
Nov 9 '12 at 15:00
Amazing! That did the trick. It was the
/etc/X11/xinit/xinitrc-common file that had the SSH-AGENT line.– Phani Kumar
Nov 9 '12 at 15:00
Amazing! That did the trick. It was the
/etc/X11/xinit/xinitrc-common file that had the SSH-AGENT line.– Phani Kumar
Nov 9 '12 at 15:00
add a comment |
Had same unrecognized login problem with KDE fedora 27-29, and Jenny D's real fix (dnf reinstall fipscheck-lib) solved the problem. Many thanks Jenny D
answered 17 mins ago
Martin LeeMartin Lee
11
New contributor
Martin Lee 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 |
Had same unrecognized login problem with KDE fedora 27-29, and Jenny D's real fix (dnf reinstall fipscheck-lib) solved the problem. Many thanks Jenny D
answered 17 mins ago
Martin LeeMartin Lee
11
New contributor
Martin Lee 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 |
Had same unrecognized login problem with KDE fedora 27-29, and Jenny D's real fix (dnf reinstall fipscheck-lib) solved the problem. Many thanks Jenny D
answered 17 mins ago
Martin LeeMartin Lee
11
New contributor
Martin Lee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Had same unrecognized login problem with KDE fedora 27-29, and Jenny D's real fix (dnf reinstall fipscheck-lib) solved the problem. Many thanks Jenny D
answered 17 mins ago
Martin LeeMartin Lee
11
New contributor
Martin Lee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 17 mins ago
Martin LeeMartin Lee
11
New contributor
Martin Lee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 17 mins ago
Martin LeeMartin Lee
11
answered 17 mins ago
Martin LeeMartin Lee
11
11
New contributor
Martin Lee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Martin Lee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Martin Lee 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.
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%2f55176%2flogin-screen-reappears-after-login%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
1
I think you should start by looking at
~/.xsession-errorsand/var/log/messages– Joseph R.
Nov 8 '12 at 9:18
also
/var/log/Xorg.1.log– xenoterracide
Nov 8 '12 at 16:25
Can you log in if you do
singleuser mode? If you can't then your/etc/shadowfile might be borked.– sparticvs
Nov 8 '12 at 18:17
You can also try to start X from sommand line with
startxoptionally redirecting its stdout and stderr:startx 2>startx.err 1>startx.log– peterph
Nov 8 '12 at 20:17
sorry for the late reply. It was the X server indeed. I followed what peterph said and the startx.err file had this,
/usr/bin/ssh-agent: error while loading shared libraries: libfipscheck.so.1: cannot open shared object file: No such file or directory. xinit: connection to X server lost.I have no idea what that means. I tried disabling ssh but it doesn't help.– Phani Kumar
Nov 9 '12 at 9:35