Screen resolution error; system won't pass login screenWrong Login Screen ResolutionScreen Resolution set too...

How can I be pwned if I'm not registered on that site?

How can I handle a player who pre-plans arguments about my rulings on RAW?

Reason Why Dimensional Travelling Would be Restricted

Is divide-by-zero a security vulnerability?

When should a commit not be version tagged?

I am on the US no-fly list. What can I do in order to be allowed on flights which go through US airspace?

Pronunciation of powers

Easy code troubleshooting in wordpress

The change directory (cd) command is not working with a USB drive

CBP Reminds Travelers to Allow 72 Hours for ESTA. Why?

I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?

What can I substitute for soda pop in a sweet pork recipe?

What are these green text/line displays shown during the livestream of Crew Dragon's approach to dock with the ISS?

What if I store 10TB on azure servers and then keep the vm powered off?

chrony vs. systemd-timesyncd – What are the differences and use cases as NTP clients?

GeometricMean definition

"Murder!" The knight said

Is there a low-level alternative to Animate Objects?

Has the Isbell–Freyd criterion ever been used to check that a category is concretisable?

Why is working on the same position for more than 15 years not a red flag?

What am I? I am in theaters and computer programs

How do ISS astronauts "get their stripes"?

What is the wife of a henpecked husband called?

Understanding Kramnik's play in game 1 of Candidates 2018



Screen resolution error; system won't pass login screen


Wrong Login Screen ResolutionScreen Resolution set too highHow to change login screen resolution?Set graphics to only use one third of a screenUbuntu 14.04.1 LTS never remember primary screen/monitor resolutionScreen position changed after changing resolution using xrandrLowest screen resolution after closed laptop screen on external monitorCan't set more resolutionresolution in ubuntu 14.04Screen resolution not appearing













0















The strangest thing happened to my system. Suddenly, it seems Ubuntu wasn't able to recognize my monitor resolution, so I wasn't able to see the graphical system through my screen. It was like when the computer is off but the monitor is on, the monitor shows a standard message asking to verify connection with the computer and cables.



After verifying connections and etc, trying a few times through different methods, finally I was able to boot into the system and the screen was working, but monitor resolution was all messed up, it had somehow changed to 'Auto' and it was all widened up. I don't understand why this happened. I was working on the computer and went downstairs to get a coffee, when I came back this stuff was happening.



I honestly don't get it if the problem was with the screen or with Ubuntu, but anyway, when I was able to work with the system I decided to change resolution manually to 1920x1080. I guess I did something wrong there, because now when I try to log in to the system, the screen that asks for my user and password shows just fine, with the usual size and all, but when I enter the password and confirm, my monitor shows a message asking to verify the connection with the computer (this happens when the computer is off and monitor is on, or if there is a problem with the cables...). But it's not the case.



This would seem like a problem with the monitor itself, but it is not, since I am able to boot on and work with Ubuntu in recovery mode, using the same monitor.



Can anyone clarify what is happening here? How do I change my monitor settings back to auto, or something that makes me able to boot into my system sucessfully (outside of recovery mode). Monitor is connected through a RGB-PC cable and system is Ubuntu 18.04.2 LTS (Lubuntu).



I guess the only way to change the monitor resolution in my main system would be through the command line in recovery mode, so how should I do that? Anyway, sorry if it is a bit confuse, I am confused myself. I can clarify any points if necessary.



Thanks!










share|improve this question









New contributor




Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • I am clueless, don't know why this happened and don't know how to fix it since I cannot login and use the system normally. Can only sucessfully login to the UI in recovery mode, but changes won't apply to main system.

    – Yara Yara
    17 mins ago
















0















The strangest thing happened to my system. Suddenly, it seems Ubuntu wasn't able to recognize my monitor resolution, so I wasn't able to see the graphical system through my screen. It was like when the computer is off but the monitor is on, the monitor shows a standard message asking to verify connection with the computer and cables.



After verifying connections and etc, trying a few times through different methods, finally I was able to boot into the system and the screen was working, but monitor resolution was all messed up, it had somehow changed to 'Auto' and it was all widened up. I don't understand why this happened. I was working on the computer and went downstairs to get a coffee, when I came back this stuff was happening.



I honestly don't get it if the problem was with the screen or with Ubuntu, but anyway, when I was able to work with the system I decided to change resolution manually to 1920x1080. I guess I did something wrong there, because now when I try to log in to the system, the screen that asks for my user and password shows just fine, with the usual size and all, but when I enter the password and confirm, my monitor shows a message asking to verify the connection with the computer (this happens when the computer is off and monitor is on, or if there is a problem with the cables...). But it's not the case.



This would seem like a problem with the monitor itself, but it is not, since I am able to boot on and work with Ubuntu in recovery mode, using the same monitor.



Can anyone clarify what is happening here? How do I change my monitor settings back to auto, or something that makes me able to boot into my system sucessfully (outside of recovery mode). Monitor is connected through a RGB-PC cable and system is Ubuntu 18.04.2 LTS (Lubuntu).



I guess the only way to change the monitor resolution in my main system would be through the command line in recovery mode, so how should I do that? Anyway, sorry if it is a bit confuse, I am confused myself. I can clarify any points if necessary.



Thanks!










share|improve this question









New contributor




Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • I am clueless, don't know why this happened and don't know how to fix it since I cannot login and use the system normally. Can only sucessfully login to the UI in recovery mode, but changes won't apply to main system.

    – Yara Yara
    17 mins ago














0












0








0








The strangest thing happened to my system. Suddenly, it seems Ubuntu wasn't able to recognize my monitor resolution, so I wasn't able to see the graphical system through my screen. It was like when the computer is off but the monitor is on, the monitor shows a standard message asking to verify connection with the computer and cables.



After verifying connections and etc, trying a few times through different methods, finally I was able to boot into the system and the screen was working, but monitor resolution was all messed up, it had somehow changed to 'Auto' and it was all widened up. I don't understand why this happened. I was working on the computer and went downstairs to get a coffee, when I came back this stuff was happening.



I honestly don't get it if the problem was with the screen or with Ubuntu, but anyway, when I was able to work with the system I decided to change resolution manually to 1920x1080. I guess I did something wrong there, because now when I try to log in to the system, the screen that asks for my user and password shows just fine, with the usual size and all, but when I enter the password and confirm, my monitor shows a message asking to verify the connection with the computer (this happens when the computer is off and monitor is on, or if there is a problem with the cables...). But it's not the case.



This would seem like a problem with the monitor itself, but it is not, since I am able to boot on and work with Ubuntu in recovery mode, using the same monitor.



Can anyone clarify what is happening here? How do I change my monitor settings back to auto, or something that makes me able to boot into my system sucessfully (outside of recovery mode). Monitor is connected through a RGB-PC cable and system is Ubuntu 18.04.2 LTS (Lubuntu).



I guess the only way to change the monitor resolution in my main system would be through the command line in recovery mode, so how should I do that? Anyway, sorry if it is a bit confuse, I am confused myself. I can clarify any points if necessary.



Thanks!










share|improve this question









New contributor




Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












The strangest thing happened to my system. Suddenly, it seems Ubuntu wasn't able to recognize my monitor resolution, so I wasn't able to see the graphical system through my screen. It was like when the computer is off but the monitor is on, the monitor shows a standard message asking to verify connection with the computer and cables.



After verifying connections and etc, trying a few times through different methods, finally I was able to boot into the system and the screen was working, but monitor resolution was all messed up, it had somehow changed to 'Auto' and it was all widened up. I don't understand why this happened. I was working on the computer and went downstairs to get a coffee, when I came back this stuff was happening.



I honestly don't get it if the problem was with the screen or with Ubuntu, but anyway, when I was able to work with the system I decided to change resolution manually to 1920x1080. I guess I did something wrong there, because now when I try to log in to the system, the screen that asks for my user and password shows just fine, with the usual size and all, but when I enter the password and confirm, my monitor shows a message asking to verify the connection with the computer (this happens when the computer is off and monitor is on, or if there is a problem with the cables...). But it's not the case.



This would seem like a problem with the monitor itself, but it is not, since I am able to boot on and work with Ubuntu in recovery mode, using the same monitor.



Can anyone clarify what is happening here? How do I change my monitor settings back to auto, or something that makes me able to boot into my system sucessfully (outside of recovery mode). Monitor is connected through a RGB-PC cable and system is Ubuntu 18.04.2 LTS (Lubuntu).



I guess the only way to change the monitor resolution in my main system would be through the command line in recovery mode, so how should I do that? Anyway, sorry if it is a bit confuse, I am confused myself. I can clarify any points if necessary.



Thanks!







lubuntu display screen display-resolution






share|improve this question









New contributor




Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 15 mins ago







Yara Yara













New contributor




Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 22 mins ago









Yara YaraYara Yara

11




11




New contributor




Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Yara Yara is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • I am clueless, don't know why this happened and don't know how to fix it since I cannot login and use the system normally. Can only sucessfully login to the UI in recovery mode, but changes won't apply to main system.

    – Yara Yara
    17 mins ago



















  • I am clueless, don't know why this happened and don't know how to fix it since I cannot login and use the system normally. Can only sucessfully login to the UI in recovery mode, but changes won't apply to main system.

    – Yara Yara
    17 mins ago

















I am clueless, don't know why this happened and don't know how to fix it since I cannot login and use the system normally. Can only sucessfully login to the UI in recovery mode, but changes won't apply to main system.

– Yara Yara
17 mins ago





I am clueless, don't know why this happened and don't know how to fix it since I cannot login and use the system normally. Can only sucessfully login to the UI in recovery mode, but changes won't apply to main system.

– Yara Yara
17 mins ago










0






active

oldest

votes











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
});


}
});






Yara Yara is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1123107%2fscreen-resolution-error-system-wont-pass-login-screen%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








Yara Yara is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Yara Yara is a new contributor. Be nice, and check out our Code of Conduct.













Yara Yara is a new contributor. Be nice, and check out our Code of Conduct.












Yara Yara is a new contributor. Be nice, and check out our Code of Conduct.
















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














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1123107%2fscreen-resolution-error-system-wont-pass-login-screen%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...