can't boot Linux due to Login service failing to start

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
1
down vote

favorite












I am having a bit of trouble with my linux mint 18.3 (based on Ubuntu 16.04) since I can't manage to properly boot it on my computer.
I have a dual-boot and windows launch properly, so there is that.



I used grub to boot Linux after switching quiet splash to nomodeset in the boot command and I got those errors :
top quality picture, isn't it ?



I used this good old google to get some info and the only things I could find didn't really help me solve my problems.
Someone had conflict with SELinux and it is not installed on my computer.



I also tried to check systemctl status *** but ctrl+alt+F1 doesn't give me any shell prompt. Even in recovery mode, I can only access the root shell prompt before the system tries to boot, once the failure occurs, the shell prompt becomes unavailable for some reasons.



I did manage to get a tty1 by using upstart, so I have access to my drive (and I am currently saving my files on a remote server before performing anymore tinkering) but the tty interface is not really the most user-friendly interface to work with, especially since I am usually working with software such as Qgis. (I am making maps)



Can I do anything to get my computer to boot properly ?
I would rather do this than reinstalling Linux.



thank you for reading.







share|improve this question





















  • From the tty try: systemctl isolate graphica.target after logging in. That's a command to manually start a graphical session. If it doesn't succeed, maybe there will be some useful debugging output.
    – Mark Stosberg
    Aug 3 at 14:43











  • "I can only access the root shell prompt before the system tries to boot " How can you get shell before the system boot? "I did manage to get a tty1 by using upstate" Upstate?
    – ç¥žç§˜å¾·é‡Œå…‹
    Aug 3 at 15:15











  • 18.3 is bugged, nothing but problems, reinstall previous version. they really dropped the ball with that release.
    – ajeh
    Aug 3 at 18:28










  • I might just reinstall, yeah. I'll probably get back to a previous more stable version.
    – laH_0009
    23 hours ago
















up vote
1
down vote

favorite












I am having a bit of trouble with my linux mint 18.3 (based on Ubuntu 16.04) since I can't manage to properly boot it on my computer.
I have a dual-boot and windows launch properly, so there is that.



I used grub to boot Linux after switching quiet splash to nomodeset in the boot command and I got those errors :
top quality picture, isn't it ?



I used this good old google to get some info and the only things I could find didn't really help me solve my problems.
Someone had conflict with SELinux and it is not installed on my computer.



I also tried to check systemctl status *** but ctrl+alt+F1 doesn't give me any shell prompt. Even in recovery mode, I can only access the root shell prompt before the system tries to boot, once the failure occurs, the shell prompt becomes unavailable for some reasons.



I did manage to get a tty1 by using upstart, so I have access to my drive (and I am currently saving my files on a remote server before performing anymore tinkering) but the tty interface is not really the most user-friendly interface to work with, especially since I am usually working with software such as Qgis. (I am making maps)



Can I do anything to get my computer to boot properly ?
I would rather do this than reinstalling Linux.



thank you for reading.







share|improve this question





















  • From the tty try: systemctl isolate graphica.target after logging in. That's a command to manually start a graphical session. If it doesn't succeed, maybe there will be some useful debugging output.
    – Mark Stosberg
    Aug 3 at 14:43











  • "I can only access the root shell prompt before the system tries to boot " How can you get shell before the system boot? "I did manage to get a tty1 by using upstate" Upstate?
    – ç¥žç§˜å¾·é‡Œå…‹
    Aug 3 at 15:15











  • 18.3 is bugged, nothing but problems, reinstall previous version. they really dropped the ball with that release.
    – ajeh
    Aug 3 at 18:28










  • I might just reinstall, yeah. I'll probably get back to a previous more stable version.
    – laH_0009
    23 hours ago












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I am having a bit of trouble with my linux mint 18.3 (based on Ubuntu 16.04) since I can't manage to properly boot it on my computer.
I have a dual-boot and windows launch properly, so there is that.



I used grub to boot Linux after switching quiet splash to nomodeset in the boot command and I got those errors :
top quality picture, isn't it ?



I used this good old google to get some info and the only things I could find didn't really help me solve my problems.
Someone had conflict with SELinux and it is not installed on my computer.



I also tried to check systemctl status *** but ctrl+alt+F1 doesn't give me any shell prompt. Even in recovery mode, I can only access the root shell prompt before the system tries to boot, once the failure occurs, the shell prompt becomes unavailable for some reasons.



I did manage to get a tty1 by using upstart, so I have access to my drive (and I am currently saving my files on a remote server before performing anymore tinkering) but the tty interface is not really the most user-friendly interface to work with, especially since I am usually working with software such as Qgis. (I am making maps)



Can I do anything to get my computer to boot properly ?
I would rather do this than reinstalling Linux.



thank you for reading.







share|improve this question













I am having a bit of trouble with my linux mint 18.3 (based on Ubuntu 16.04) since I can't manage to properly boot it on my computer.
I have a dual-boot and windows launch properly, so there is that.



I used grub to boot Linux after switching quiet splash to nomodeset in the boot command and I got those errors :
top quality picture, isn't it ?



I used this good old google to get some info and the only things I could find didn't really help me solve my problems.
Someone had conflict with SELinux and it is not installed on my computer.



I also tried to check systemctl status *** but ctrl+alt+F1 doesn't give me any shell prompt. Even in recovery mode, I can only access the root shell prompt before the system tries to boot, once the failure occurs, the shell prompt becomes unavailable for some reasons.



I did manage to get a tty1 by using upstart, so I have access to my drive (and I am currently saving my files on a remote server before performing anymore tinkering) but the tty interface is not really the most user-friendly interface to work with, especially since I am usually working with software such as Qgis. (I am making maps)



Can I do anything to get my computer to boot properly ?
I would rather do this than reinstalling Linux.



thank you for reading.









share|improve this question












share|improve this question




share|improve this question








edited Aug 3 at 17:48









Jeff Schaller

30.7k846104




30.7k846104









asked Aug 3 at 14:18









laH_0009

62




62











  • From the tty try: systemctl isolate graphica.target after logging in. That's a command to manually start a graphical session. If it doesn't succeed, maybe there will be some useful debugging output.
    – Mark Stosberg
    Aug 3 at 14:43











  • "I can only access the root shell prompt before the system tries to boot " How can you get shell before the system boot? "I did manage to get a tty1 by using upstate" Upstate?
    – ç¥žç§˜å¾·é‡Œå…‹
    Aug 3 at 15:15











  • 18.3 is bugged, nothing but problems, reinstall previous version. they really dropped the ball with that release.
    – ajeh
    Aug 3 at 18:28










  • I might just reinstall, yeah. I'll probably get back to a previous more stable version.
    – laH_0009
    23 hours ago
















  • From the tty try: systemctl isolate graphica.target after logging in. That's a command to manually start a graphical session. If it doesn't succeed, maybe there will be some useful debugging output.
    – Mark Stosberg
    Aug 3 at 14:43











  • "I can only access the root shell prompt before the system tries to boot " How can you get shell before the system boot? "I did manage to get a tty1 by using upstate" Upstate?
    – ç¥žç§˜å¾·é‡Œå…‹
    Aug 3 at 15:15











  • 18.3 is bugged, nothing but problems, reinstall previous version. they really dropped the ball with that release.
    – ajeh
    Aug 3 at 18:28










  • I might just reinstall, yeah. I'll probably get back to a previous more stable version.
    – laH_0009
    23 hours ago















From the tty try: systemctl isolate graphica.target after logging in. That's a command to manually start a graphical session. If it doesn't succeed, maybe there will be some useful debugging output.
– Mark Stosberg
Aug 3 at 14:43





From the tty try: systemctl isolate graphica.target after logging in. That's a command to manually start a graphical session. If it doesn't succeed, maybe there will be some useful debugging output.
– Mark Stosberg
Aug 3 at 14:43













"I can only access the root shell prompt before the system tries to boot " How can you get shell before the system boot? "I did manage to get a tty1 by using upstate" Upstate?
– ç¥žç§˜å¾·é‡Œå…‹
Aug 3 at 15:15





"I can only access the root shell prompt before the system tries to boot " How can you get shell before the system boot? "I did manage to get a tty1 by using upstate" Upstate?
– ç¥žç§˜å¾·é‡Œå…‹
Aug 3 at 15:15













18.3 is bugged, nothing but problems, reinstall previous version. they really dropped the ball with that release.
– ajeh
Aug 3 at 18:28




18.3 is bugged, nothing but problems, reinstall previous version. they really dropped the ball with that release.
– ajeh
Aug 3 at 18:28












I might just reinstall, yeah. I'll probably get back to a previous more stable version.
– laH_0009
23 hours ago




I might just reinstall, yeah. I'll probably get back to a previous more stable version.
– laH_0009
23 hours ago















active

oldest

votes











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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f460341%2fcant-boot-linux-due-to-login-service-failing-to-start%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f460341%2fcant-boot-linux-due-to-login-service-failing-to-start%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay