No graphical interface after editing /etc/default/grub
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
After some research in the try of solving a problem with sound in Ubuntu 18.04, I found some answers involving editing of the file /etc/default/grub. After playing with this file and rebooting, surprisingly, Ubuntu booted in terminal mode instead of graphical.
Then, I did some search on how to get back to GUI from CLI, but every solution I found just didn't work (I tried startx command so as to start GUI, but it holds for some time and then times out saying "time out in locking authority file").
Also I tried init 5 but this also shows GUI for a blink of an eye and then gets back into the terminal. I tried the Alt + Ctrl + F7 combination, but it appears that it does nothing.
I tried to reinstall ubuntu-desktop, but it faced broken packaged and failed to do so; afterward I got to know that aptitude could possibly solve this issue automatically, but it didn't.
I'm new to Ubuntu and any measure I take at this step seem to worsen the situation!! Any help would be appreciated.
boot grub2 18.04
edited Mar 28 at 20:31
Olimjon
2,336824
asked Mar 28 at 20:09
Saber DinpashohSaber Dinpashoh
1
add a comment |
After some research in the try of solving a problem with sound in Ubuntu 18.04, I found some answers involving editing of the file /etc/default/grub. After playing with this file and rebooting, surprisingly, Ubuntu booted in terminal mode instead of graphical.
Then, I did some search on how to get back to GUI from CLI, but every solution I found just didn't work (I tried startx command so as to start GUI, but it holds for some time and then times out saying "time out in locking authority file").
Also I tried init 5 but this also shows GUI for a blink of an eye and then gets back into the terminal. I tried the Alt + Ctrl + F7 combination, but it appears that it does nothing.
I tried to reinstall ubuntu-desktop, but it faced broken packaged and failed to do so; afterward I got to know that aptitude could possibly solve this issue automatically, but it didn't.
I'm new to Ubuntu and any measure I take at this step seem to worsen the situation!! Any help would be appreciated.
boot grub2 18.04
edited Mar 28 at 20:31
Olimjon
2,336824
asked Mar 28 at 20:09
Saber DinpashohSaber Dinpashoh
1
1
What changes did you make to /etc/default/grub? Did you runsudo update-grubafterwards?
– Charles Green
Mar 28 at 20:38
As Charles suggested, it would be helpful to know what changes you made to /etc/default/grub. Also, you may want to have a look at this: askubuntu.com/a/729211/787506. As for fixing broken packages, see this: askubuntu.com/a/1028516/787506
– Hee Jin
Mar 28 at 21:02
To be exact I added some numbers before "quiet splash" phrase at GRUB_CMDLINE_LINUX_DEFAULT and yes I did update-grub command .but as soon as I realized that the cause of the problem is this I reverted the file to its initial state but the problem didn't solve.
– Saber Dinpashoh
Mar 28 at 21:22
add a comment |
After some research in the try of solving a problem with sound in Ubuntu 18.04, I found some answers involving editing of the file /etc/default/grub. After playing with this file and rebooting, surprisingly, Ubuntu booted in terminal mode instead of graphical.
Then, I did some search on how to get back to GUI from CLI, but every solution I found just didn't work (I tried startx command so as to start GUI, but it holds for some time and then times out saying "time out in locking authority file").
Also I tried init 5 but this also shows GUI for a blink of an eye and then gets back into the terminal. I tried the Alt + Ctrl + F7 combination, but it appears that it does nothing.
I tried to reinstall ubuntu-desktop, but it faced broken packaged and failed to do so; afterward I got to know that aptitude could possibly solve this issue automatically, but it didn't.
I'm new to Ubuntu and any measure I take at this step seem to worsen the situation!! Any help would be appreciated.
boot grub2 18.04
edited Mar 28 at 20:31
Olimjon
2,336824
asked Mar 28 at 20:09
Saber DinpashohSaber Dinpashoh
1
After some research in the try of solving a problem with sound in Ubuntu 18.04, I found some answers involving editing of the file /etc/default/grub. After playing with this file and rebooting, surprisingly, Ubuntu booted in terminal mode instead of graphical.
Then, I did some search on how to get back to GUI from CLI, but every solution I found just didn't work (I tried startx command so as to start GUI, but it holds for some time and then times out saying "time out in locking authority file").
Also I tried init 5 but this also shows GUI for a blink of an eye and then gets back into the terminal. I tried the Alt + Ctrl + F7 combination, but it appears that it does nothing.
I tried to reinstall ubuntu-desktop, but it faced broken packaged and failed to do so; afterward I got to know that aptitude could possibly solve this issue automatically, but it didn't.
I'm new to Ubuntu and any measure I take at this step seem to worsen the situation!! Any help would be appreciated.
boot grub2 18.04
boot grub2 18.04
edited Mar 28 at 20:31
Olimjon
2,336824
asked Mar 28 at 20:09
Saber DinpashohSaber Dinpashoh
1
edited Mar 28 at 20:31
Olimjon
2,336824
asked Mar 28 at 20:09
Saber DinpashohSaber Dinpashoh
1
edited Mar 28 at 20:31
Olimjon
2,336824
edited Mar 28 at 20:31
Olimjon
2,336824
edited Mar 28 at 20:31
Olimjon
2,336824
2,336824
asked Mar 28 at 20:09
Saber DinpashohSaber Dinpashoh
1
asked Mar 28 at 20:09
Saber DinpashohSaber Dinpashoh
1
asked Mar 28 at 20:09
Saber DinpashohSaber Dinpashoh
1
1
1
What changes did you make to /etc/default/grub? Did you runsudo update-grubafterwards?
– Charles Green
Mar 28 at 20:38
As Charles suggested, it would be helpful to know what changes you made to /etc/default/grub. Also, you may want to have a look at this: askubuntu.com/a/729211/787506. As for fixing broken packages, see this: askubuntu.com/a/1028516/787506
– Hee Jin
Mar 28 at 21:02
To be exact I added some numbers before "quiet splash" phrase at GRUB_CMDLINE_LINUX_DEFAULT and yes I did update-grub command .but as soon as I realized that the cause of the problem is this I reverted the file to its initial state but the problem didn't solve.
– Saber Dinpashoh
Mar 28 at 21:22
add a comment |
1
What changes did you make to /etc/default/grub? Did you runsudo update-grubafterwards?
– Charles Green
Mar 28 at 20:38
As Charles suggested, it would be helpful to know what changes you made to /etc/default/grub. Also, you may want to have a look at this: askubuntu.com/a/729211/787506. As for fixing broken packages, see this: askubuntu.com/a/1028516/787506
– Hee Jin
Mar 28 at 21:02
To be exact I added some numbers before "quiet splash" phrase at GRUB_CMDLINE_LINUX_DEFAULT and yes I did update-grub command .but as soon as I realized that the cause of the problem is this I reverted the file to its initial state but the problem didn't solve.
– Saber Dinpashoh
Mar 28 at 21:22
1
1
What changes did you make to /etc/default/grub? Did you run
sudo update-grub afterwards?– Charles Green
Mar 28 at 20:38
What changes did you make to /etc/default/grub? Did you run
sudo update-grub afterwards?– Charles Green
Mar 28 at 20:38
As Charles suggested, it would be helpful to know what changes you made to /etc/default/grub. Also, you may want to have a look at this: askubuntu.com/a/729211/787506. As for fixing broken packages, see this: askubuntu.com/a/1028516/787506
– Hee Jin
Mar 28 at 21:02
As Charles suggested, it would be helpful to know what changes you made to /etc/default/grub. Also, you may want to have a look at this: askubuntu.com/a/729211/787506. As for fixing broken packages, see this: askubuntu.com/a/1028516/787506
– Hee Jin
Mar 28 at 21:02
To be exact I added some numbers before "quiet splash" phrase at GRUB_CMDLINE_LINUX_DEFAULT and yes I did update-grub command .but as soon as I realized that the cause of the problem is this I reverted the file to its initial state but the problem didn't solve.
– Saber Dinpashoh
Mar 28 at 21:22
To be exact I added some numbers before "quiet splash" phrase at GRUB_CMDLINE_LINUX_DEFAULT and yes I did update-grub command .but as soon as I realized that the cause of the problem is this I reverted the file to its initial state but the problem didn't solve.
– Saber Dinpashoh
Mar 28 at 21:22
add a comment |
1 Answer
1
active
oldest
votes
To fix your /etc/default/grub, do:
sudo nano /etc/default/grub
Remove everything and add these (default Ubuntu grub file instructions excluding comments):
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
Save using Ctrl+X.
Then do:
sudo update-grub
answered Mar 28 at 20:37
OlimjonOlimjon
2,336824
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1129501%2fno-graphical-interface-after-editing-etc-default-grub%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
To fix your /etc/default/grub, do:
sudo nano /etc/default/grub
Remove everything and add these (default Ubuntu grub file instructions excluding comments):
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
Save using Ctrl+X.
Then do:
sudo update-grub
answered Mar 28 at 20:37
OlimjonOlimjon
2,336824
add a comment |
To fix your /etc/default/grub, do:
sudo nano /etc/default/grub
Remove everything and add these (default Ubuntu grub file instructions excluding comments):
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
Save using Ctrl+X.
Then do:
sudo update-grub
answered Mar 28 at 20:37
OlimjonOlimjon
2,336824
add a comment |
To fix your /etc/default/grub, do:
sudo nano /etc/default/grub
Remove everything and add these (default Ubuntu grub file instructions excluding comments):
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
Save using Ctrl+X.
Then do:
sudo update-grub
answered Mar 28 at 20:37
OlimjonOlimjon
2,336824
To fix your /etc/default/grub, do:
sudo nano /etc/default/grub
Remove everything and add these (default Ubuntu grub file instructions excluding comments):
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
Save using Ctrl+X.
Then do:
sudo update-grub
answered Mar 28 at 20:37
OlimjonOlimjon
2,336824
edited Mar 28 at 20:48
answered Mar 28 at 20:37
OlimjonOlimjon
2,336824
answered Mar 28 at 20:37
OlimjonOlimjon
2,336824
answered Mar 28 at 20:37
OlimjonOlimjon
2,336824
2,336824
add a comment |
add a comment |
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.
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%2faskubuntu.com%2fquestions%2f1129501%2fno-graphical-interface-after-editing-etc-default-grub%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
What changes did you make to /etc/default/grub? Did you run
sudo update-grubafterwards?– Charles Green
Mar 28 at 20:38
As Charles suggested, it would be helpful to know what changes you made to /etc/default/grub. Also, you may want to have a look at this: askubuntu.com/a/729211/787506. As for fixing broken packages, see this: askubuntu.com/a/1028516/787506
– Hee Jin
Mar 28 at 21:02
To be exact I added some numbers before "quiet splash" phrase at GRUB_CMDLINE_LINUX_DEFAULT and yes I did update-grub command .but as soon as I realized that the cause of the problem is this I reverted the file to its initial state but the problem didn't solve.
– Saber Dinpashoh
Mar 28 at 21:22