Login loop after base update on Ubuntu 18.04.1

I have exactly the same problem with this answer. I don't understand why that topic is closed.

I cannot login my desktop for first time after using and trusting the new Ubuntu so many months already.

I have compared my updates history with the link I posted above and I m quite sure that the culprit is on one of these two updates:

libgjs0g:amd64

gjs:amd64

PS. I don't want to upgrade to 18.10...wanna stay LTS

edited Jan 18 at 17:09

asked Jan 18 at 14:08

Georgens

163

once i had a log in loop because i went out of space, if i remember well. by doing sudo apt-get -y autoremove && sudo apt-get -y clean the problem was solved. perhaps you can log in if u switch to another session with CTRL+F2 or try the recovery mode and run the command on that level -> see: askubuntu.com/questions/24006/…

– AlexOnLinux
Jan 18 at 14:13

For sure I am not out of space. I think it's not a coincidence that two of my updates are the same with the other guy's updates in the link I posted before.thanks anyway

– Georgens
Jan 18 at 14:49

I have tried all the old tricks related to the same login loop issue, stop&restart gdm,chown the .iceauthority etc. None of them works!

– Georgens
Jan 18 at 15:04

In your question, you write that you think you know the culprit. If so, then what sort of help are you asking for? The question you want answered does not seem clear.

– user535733
Jan 18 at 15:23

I just provide some information that maybe can shed some light what causes that loop. That I found, probably, the cause doesn't mean I can solve it. I can't remove these two packages,and I can't go back downgrading to previous version. Just an basic update routine turned to be a nightmare,so if anyone can help would be nice

– Georgens
Jan 18 at 15:35

|
show 1 more comment

I have exactly the same problem with this answer. I don't understand why that topic is closed.

I cannot login my desktop for first time after using and trusting the new Ubuntu so many months already.

I have compared my updates history with the link I posted above and I m quite sure that the culprit is on one of these two updates:

libgjs0g:amd64

gjs:amd64

PS. I don't want to upgrade to 18.10...wanna stay LTS

edited Jan 18 at 17:09

asked Jan 18 at 14:08

Georgens

163

once i had a log in loop because i went out of space, if i remember well. by doing sudo apt-get -y autoremove && sudo apt-get -y clean the problem was solved. perhaps you can log in if u switch to another session with CTRL+F2 or try the recovery mode and run the command on that level -> see: askubuntu.com/questions/24006/…

– AlexOnLinux
Jan 18 at 14:13

For sure I am not out of space. I think it's not a coincidence that two of my updates are the same with the other guy's updates in the link I posted before.thanks anyway

– Georgens
Jan 18 at 14:49

I have tried all the old tricks related to the same login loop issue, stop&restart gdm,chown the .iceauthority etc. None of them works!

– Georgens
Jan 18 at 15:04

In your question, you write that you think you know the culprit. If so, then what sort of help are you asking for? The question you want answered does not seem clear.

– user535733
Jan 18 at 15:23

I just provide some information that maybe can shed some light what causes that loop. That I found, probably, the cause doesn't mean I can solve it. I can't remove these two packages,and I can't go back downgrading to previous version. Just an basic update routine turned to be a nightmare,so if anyone can help would be nice

– Georgens
Jan 18 at 15:35

|
show 1 more comment

I have exactly the same problem with this answer. I don't understand why that topic is closed.

I cannot login my desktop for first time after using and trusting the new Ubuntu so many months already.

I have compared my updates history with the link I posted above and I m quite sure that the culprit is on one of these two updates:

libgjs0g:amd64

gjs:amd64

PS. I don't want to upgrade to 18.10...wanna stay LTS

edited Jan 18 at 17:09

asked Jan 18 at 14:08

Georgens

163

I have exactly the same problem with this answer. I don't understand why that topic is closed.

I cannot login my desktop for first time after using and trusting the new Ubuntu so many months already.

I have compared my updates history with the link I posted above and I m quite sure that the culprit is on one of these two updates:

libgjs0g:amd64

gjs:amd64

PS. I don't want to upgrade to 18.10...wanna stay LTS

upgrade login

edited Jan 18 at 17:09

asked Jan 18 at 14:08

Georgens

163

edited Jan 18 at 17:09

asked Jan 18 at 14:08

Georgens

163

edited Jan 18 at 17:09

asked Jan 18 at 14:08

Georgens

163

asked Jan 18 at 14:08

Georgens

163

asked Jan 18 at 14:08

Georgens

163

once i had a log in loop because i went out of space, if i remember well. by doing sudo apt-get -y autoremove && sudo apt-get -y clean the problem was solved. perhaps you can log in if u switch to another session with CTRL+F2 or try the recovery mode and run the command on that level -> see: askubuntu.com/questions/24006/…

– AlexOnLinux
Jan 18 at 14:13

For sure I am not out of space. I think it's not a coincidence that two of my updates are the same with the other guy's updates in the link I posted before.thanks anyway

– Georgens
Jan 18 at 14:49

I have tried all the old tricks related to the same login loop issue, stop&restart gdm,chown the .iceauthority etc. None of them works!

– Georgens
Jan 18 at 15:04

In your question, you write that you think you know the culprit. If so, then what sort of help are you asking for? The question you want answered does not seem clear.

– user535733
Jan 18 at 15:23

I just provide some information that maybe can shed some light what causes that loop. That I found, probably, the cause doesn't mean I can solve it. I can't remove these two packages,and I can't go back downgrading to previous version. Just an basic update routine turned to be a nightmare,so if anyone can help would be nice

– Georgens
Jan 18 at 15:35

|
show 1 more comment

once i had a log in loop because i went out of space, if i remember well. by doing sudo apt-get -y autoremove && sudo apt-get -y clean the problem was solved. perhaps you can log in if u switch to another session with CTRL+F2 or try the recovery mode and run the command on that level -> see: askubuntu.com/questions/24006/…

– AlexOnLinux
Jan 18 at 14:13

For sure I am not out of space. I think it's not a coincidence that two of my updates are the same with the other guy's updates in the link I posted before.thanks anyway

– Georgens
Jan 18 at 14:49

I have tried all the old tricks related to the same login loop issue, stop&restart gdm,chown the .iceauthority etc. None of them works!

– Georgens
Jan 18 at 15:04

In your question, you write that you think you know the culprit. If so, then what sort of help are you asking for? The question you want answered does not seem clear.

– user535733
Jan 18 at 15:23

I just provide some information that maybe can shed some light what causes that loop. That I found, probably, the cause doesn't mean I can solve it. I can't remove these two packages,and I can't go back downgrading to previous version. Just an basic update routine turned to be a nightmare,so if anyone can help would be nice

– Georgens
Jan 18 at 15:35

once i had a log in loop because i went out of space, if i remember well. by doing sudo apt-get -y autoremove && sudo apt-get -y clean the problem was solved. perhaps you can log in if u switch to another session with CTRL+F2 or try the recovery mode and run the command on that level -> see: askubuntu.com/questions/24006/…

– AlexOnLinux
Jan 18 at 14:13

For sure I am not out of space. I think it's not a coincidence that two of my updates are the same with the other guy's updates in the link I posted before.thanks anyway

– Georgens
Jan 18 at 14:49

I have tried all the old tricks related to the same login loop issue, stop&restart gdm,chown the .iceauthority etc. None of them works!

– Georgens
Jan 18 at 15:04

In your question, you write that you think you know the culprit. If so, then what sort of help are you asking for? The question you want answered does not seem clear.

– user535733
Jan 18 at 15:23

I just provide some information that maybe can shed some light what causes that loop. That I found, probably, the cause doesn't mean I can solve it. I can't remove these two packages,and I can't go back downgrading to previous version. Just an basic update routine turned to be a nightmare,so if anyone can help would be nice

– Georgens
Jan 18 at 15:35

|
show 1 more comment

3 Answers
3

active

oldest

votes

SO I WAS RIGHT.
Finally I managed to downgrade the gjs and libgjs0 to the previous version and solved my problem.

Now I have to prevent this particular update to happen...
HOPE PEOPLE WILL BE MORE CAREFUL WITH UPDATES...

Update:
I followed this link to roll back and prevent:
Is there any way to roll back the most recent upgrade?

Locking version from synaptic is also an option to block the updates.
Cheers

edited Jan 21 at 23:31

answered Jan 19 at 3:10

Georgens

163

Congratulations! You solved my problem too! I had reinstalled 18.04.1 without any updates, but now I've blocked gjs' and libgjs0g' version to 1.52.1 (in Synaptic) to prevent the update to 1.52.5, then I've updated my system and all works fine. Thanks!

– Sergio
Jan 20 at 21:55

Great that worked! It would kill me to reinstall the OS again along with all my stuff,so I followed this after Ctrl+alt+f3 ...askubuntu.com/questions/34888/…

– Georgens
Jan 21 at 23:21

add a comment |

I was having the same problem, but went for a different solution:

I noticed that if I created a new user the login of that user went fine. I assumed then the problem was in my user config.
So I made a backup of my home folder and removed my original user.

Then I created it again and login was successful. Of course I have lost all my configs, but the programs were still installed. Then I started to copy back folder by folder from my backup home to my new, clean, home.

I narrowed down the issue to the gnome extensions folder. As soon as I copied it back, the login loop happened again. I can't tell which extension was causing the issue, because I removed the extensions folder and reinstalled them using Chrome.

the folder location is: HOME/.local/share/gnome-shell/extensions

Hope this helps users that had this issue. It was quite painful to see a LTS block in that way.

Cheers

answered Jan 21 at 10:42

procopiostein

As to which extension was causing the issue, did you install workspace-grid?

– Sergio
Jan 22 at 20:51

add a comment |

In my case, the problem was the app indicator-multiload, that I had recently installed. So, the solution was simply

sudo apt remove indicator-multiload

I suspect it must have collapsed somehow with the GNOME extensions, in the line of procopiostein's answer .

edited yesterday

answered yesterday

alexhg

New contributor

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1110886%2flogin-loop-after-base-update-on-ubuntu-18-04-1%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

SO I WAS RIGHT.
Finally I managed to downgrade the gjs and libgjs0 to the previous version and solved my problem.

Now I have to prevent this particular update to happen...
HOPE PEOPLE WILL BE MORE CAREFUL WITH UPDATES...

Update:
I followed this link to roll back and prevent:
Is there any way to roll back the most recent upgrade?

Locking version from synaptic is also an option to block the updates.
Cheers

edited Jan 21 at 23:31

answered Jan 19 at 3:10

Georgens

163

Congratulations! You solved my problem too! I had reinstalled 18.04.1 without any updates, but now I've blocked gjs' and libgjs0g' version to 1.52.1 (in Synaptic) to prevent the update to 1.52.5, then I've updated my system and all works fine. Thanks!

– Sergio
Jan 20 at 21:55

Great that worked! It would kill me to reinstall the OS again along with all my stuff,so I followed this after Ctrl+alt+f3 ...askubuntu.com/questions/34888/…

– Georgens
Jan 21 at 23:21

add a comment |

SO I WAS RIGHT.
Finally I managed to downgrade the gjs and libgjs0 to the previous version and solved my problem.

Now I have to prevent this particular update to happen...
HOPE PEOPLE WILL BE MORE CAREFUL WITH UPDATES...

Update:
I followed this link to roll back and prevent:
Is there any way to roll back the most recent upgrade?

Locking version from synaptic is also an option to block the updates.
Cheers

edited Jan 21 at 23:31

answered Jan 19 at 3:10

Georgens

163

Congratulations! You solved my problem too! I had reinstalled 18.04.1 without any updates, but now I've blocked gjs' and libgjs0g' version to 1.52.1 (in Synaptic) to prevent the update to 1.52.5, then I've updated my system and all works fine. Thanks!

– Sergio
Jan 20 at 21:55

Great that worked! It would kill me to reinstall the OS again along with all my stuff,so I followed this after Ctrl+alt+f3 ...askubuntu.com/questions/34888/…

– Georgens
Jan 21 at 23:21

add a comment |

SO I WAS RIGHT.
Finally I managed to downgrade the gjs and libgjs0 to the previous version and solved my problem.

Now I have to prevent this particular update to happen...
HOPE PEOPLE WILL BE MORE CAREFUL WITH UPDATES...

Update:
I followed this link to roll back and prevent:
Is there any way to roll back the most recent upgrade?

Locking version from synaptic is also an option to block the updates.
Cheers

edited Jan 21 at 23:31

answered Jan 19 at 3:10

Georgens

163

SO I WAS RIGHT.
Finally I managed to downgrade the gjs and libgjs0 to the previous version and solved my problem.

Now I have to prevent this particular update to happen...
HOPE PEOPLE WILL BE MORE CAREFUL WITH UPDATES...

Update:
I followed this link to roll back and prevent:
Is there any way to roll back the most recent upgrade?

Locking version from synaptic is also an option to block the updates.
Cheers

edited Jan 21 at 23:31

answered Jan 19 at 3:10

Georgens

163

edited Jan 21 at 23:31

answered Jan 19 at 3:10

Georgens

163

answered Jan 19 at 3:10

Georgens

163

answered Jan 19 at 3:10

Georgens

163

Congratulations! You solved my problem too! I had reinstalled 18.04.1 without any updates, but now I've blocked gjs' and libgjs0g' version to 1.52.1 (in Synaptic) to prevent the update to 1.52.5, then I've updated my system and all works fine. Thanks!

– Sergio
Jan 20 at 21:55

Great that worked! It would kill me to reinstall the OS again along with all my stuff,so I followed this after Ctrl+alt+f3 ...askubuntu.com/questions/34888/…

– Georgens
Jan 21 at 23:21

add a comment |

Congratulations! You solved my problem too! I had reinstalled 18.04.1 without any updates, but now I've blocked gjs' and libgjs0g' version to 1.52.1 (in Synaptic) to prevent the update to 1.52.5, then I've updated my system and all works fine. Thanks!

– Sergio
Jan 20 at 21:55

Great that worked! It would kill me to reinstall the OS again along with all my stuff,so I followed this after Ctrl+alt+f3 ...askubuntu.com/questions/34888/…

– Georgens
Jan 21 at 23:21

Congratulations! You solved my problem too! I had reinstalled 18.04.1 without any updates, but now I've blocked gjs' and libgjs0g' version to 1.52.1 (in Synaptic) to prevent the update to 1.52.5, then I've updated my system and all works fine. Thanks!

– Sergio
Jan 20 at 21:55

Great that worked! It would kill me to reinstall the OS again along with all my stuff,so I followed this after Ctrl+alt+f3 ...askubuntu.com/questions/34888/…

– Georgens
Jan 21 at 23:21

add a comment |

I was having the same problem, but went for a different solution:

I noticed that if I created a new user the login of that user went fine. I assumed then the problem was in my user config.
So I made a backup of my home folder and removed my original user.

the folder location is: HOME/.local/share/gnome-shell/extensions

Hope this helps users that had this issue. It was quite painful to see a LTS block in that way.

Cheers

answered Jan 21 at 10:42

procopiostein

As to which extension was causing the issue, did you install workspace-grid?

– Sergio
Jan 22 at 20:51

add a comment |

I was having the same problem, but went for a different solution:

I noticed that if I created a new user the login of that user went fine. I assumed then the problem was in my user config.
So I made a backup of my home folder and removed my original user.

the folder location is: HOME/.local/share/gnome-shell/extensions

Hope this helps users that had this issue. It was quite painful to see a LTS block in that way.

Cheers

answered Jan 21 at 10:42

procopiostein

As to which extension was causing the issue, did you install workspace-grid?

– Sergio
Jan 22 at 20:51

add a comment |

I was having the same problem, but went for a different solution:

I noticed that if I created a new user the login of that user went fine. I assumed then the problem was in my user config.
So I made a backup of my home folder and removed my original user.

the folder location is: HOME/.local/share/gnome-shell/extensions

Hope this helps users that had this issue. It was quite painful to see a LTS block in that way.

Cheers

answered Jan 21 at 10:42

procopiostein

I was having the same problem, but went for a different solution:

I noticed that if I created a new user the login of that user went fine. I assumed then the problem was in my user config.
So I made a backup of my home folder and removed my original user.

the folder location is: HOME/.local/share/gnome-shell/extensions

Hope this helps users that had this issue. It was quite painful to see a LTS block in that way.

Cheers

answered Jan 21 at 10:42

procopiostein

answered Jan 21 at 10:42

procopiostein

answered Jan 21 at 10:42

procopiostein

answered Jan 21 at 10:42

procopiostein

As to which extension was causing the issue, did you install workspace-grid?

– Sergio
Jan 22 at 20:51

add a comment |

As to which extension was causing the issue, did you install workspace-grid?

– Sergio
Jan 22 at 20:51

As to which extension was causing the issue, did you install workspace-grid?

– Sergio
Jan 22 at 20:51

add a comment |

In my case, the problem was the app indicator-multiload, that I had recently installed. So, the solution was simply

sudo apt remove indicator-multiload

I suspect it must have collapsed somehow with the GNOME extensions, in the line of procopiostein's answer .

edited yesterday

answered yesterday

alexhg

New contributor

add a comment |

In my case, the problem was the app indicator-multiload, that I had recently installed. So, the solution was simply

sudo apt remove indicator-multiload

I suspect it must have collapsed somehow with the GNOME extensions, in the line of procopiostein's answer .

edited yesterday

answered yesterday

alexhg

New contributor

add a comment |

In my case, the problem was the app indicator-multiload, that I had recently installed. So, the solution was simply

sudo apt remove indicator-multiload

I suspect it must have collapsed somehow with the GNOME extensions, in the line of procopiostein's answer .

edited yesterday

answered yesterday

alexhg

New contributor

In my case, the problem was the app indicator-multiload, that I had recently installed. So, the solution was simply

sudo apt remove indicator-multiload

I suspect it must have collapsed somehow with the GNOME extensions, in the line of procopiostein's answer .

edited yesterday

answered yesterday

alexhg

New contributor

edited yesterday

answered yesterday

alexhg

New contributor

answered yesterday

alexhg

answered yesterday

alexhg

New contributor

alexhg 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 |

draft saved

draft discarded

Thanks for contributing an answer to Ask Ubuntu!

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Ytdyklly