Not updating display settings when disconnecting external monitorHow can I change what keys on my keyboard...

Have I saved too much for retirement so far?

Does having a TSA Pre-Check member in your flight reservation increase the chances that everyone gets Pre-Check?

Is possible to search in vim history?

Do the concepts of IP address and network interface not belong to the same layer?

How should I respond when I lied about my education and the company finds out through background check?

How to align and center standalone amsmath equations?

Flux received by a negative charge

Why in book's example is used 言葉(ことば) instead of 言語(げんご)?

Is a model fitted to data or is data fitted to a model?

When quoting, must I also copy hyphens used to divide words that continue on the next line?

How much character growth crosses the line into breaking the character

What (else) happened July 1st 1858 in London?

Can someone explain how this makes sense electrically?

List of people who lose a child in תנ"ך

Is it possible to have a strip of cold climate in the middle of a planet?

My friend sent me a screenshot of a transaction hash, but when I search for it I find divergent data. What happened?

Using a siddur to Daven from in a seforim store

How do I implement a file system driver driver in Linux?

Customize circled numbers

Open a doc from terminal, but not by its name

Frequency of inspection at vegan restaurants

Java - What do constructor type arguments mean when placed *before* the type?

Difference between -| and |- in TikZ

Can I use my Chinese passport to enter China after I acquired another citizenship?



Not updating display settings when disconnecting external monitor


How can I change what keys on my keyboard do? (How can I create custom keyboard commands/shortcuts?)Is there a way to autodetect when a display is disconnected?ubuntu 13.10 secondary monitor - doesn't redraw properlyCan't detect external monitor on Thinkpad W530 running Ubuntu 14.0414.04 nvidia dual display (external+laptop) stretched display, offset desktopNVidia graphics driver cannot detect second monitorLaptop mini DisplayPort issue - external monitor does not detect on 16.04External monitor breaks display configuration randomlyDisplay monitor not resettingUbuntu 16.04 only works when secondary monitor is connectedExternal monitor not detected in 18.10External Monitor Not Working with Ubuntu 18.04 (Razer Blade 2017)













7















When I disconnect my monitor from my laptop, Ubuntu still seems to think that it is plugged in and does't update the display. This issue is Ubuntu specific (not occuring in windows) and my monitor worked fine with another laptop (Ubuntu 13.04, exact same drivers).



The quickfix:




  • open system settings

  • click Displays


Useful specs:





  • Graphics drivers: nvidia-313 (problem also occurs with the other propriatary drivers)


  • Graphics card: Nvidia Quadro K1000M


  • Monitor: Benq ET-0019-N


  • Cable: VGA D-sub DE15


  • OS: Ubuntu 13.04




I would like Ubuntu to update the display settings automagically whenever the monitor cable gets disconnected. How would I do that?










share|improve this question

























  • What monitor is it? Some older monitors don't send any signal so the computer doesn't know whether it's there, but I don't think there are many left in service. Also what exact model of graphics card do you have, and are you using the proprietary driver or the free driver?

    – Gilles
    Aug 22 '13 at 20:30











  • I've edited my question to answer yours.

    – Joren
    Aug 22 '13 at 20:42











  • The display settings are updated when you start the computer without the cable, and then attach it? If not, are they updated when you issue the command xrandr manually?

    – Jorge Suárez de Lis
    Sep 9 '13 at 9:58











  • Can't you try another monitor and cable? I know that it's working on Windows, byt maybe Windows is using another method for autodetection.

    – Jorge Suárez de Lis
    Sep 12 '13 at 12:35











  • I don't have another monitor :(

    – Joren
    Sep 12 '13 at 12:36
















7















When I disconnect my monitor from my laptop, Ubuntu still seems to think that it is plugged in and does't update the display. This issue is Ubuntu specific (not occuring in windows) and my monitor worked fine with another laptop (Ubuntu 13.04, exact same drivers).



The quickfix:




  • open system settings

  • click Displays


Useful specs:





  • Graphics drivers: nvidia-313 (problem also occurs with the other propriatary drivers)


  • Graphics card: Nvidia Quadro K1000M


  • Monitor: Benq ET-0019-N


  • Cable: VGA D-sub DE15


  • OS: Ubuntu 13.04




I would like Ubuntu to update the display settings automagically whenever the monitor cable gets disconnected. How would I do that?










share|improve this question

























  • What monitor is it? Some older monitors don't send any signal so the computer doesn't know whether it's there, but I don't think there are many left in service. Also what exact model of graphics card do you have, and are you using the proprietary driver or the free driver?

    – Gilles
    Aug 22 '13 at 20:30











  • I've edited my question to answer yours.

    – Joren
    Aug 22 '13 at 20:42











  • The display settings are updated when you start the computer without the cable, and then attach it? If not, are they updated when you issue the command xrandr manually?

    – Jorge Suárez de Lis
    Sep 9 '13 at 9:58











  • Can't you try another monitor and cable? I know that it's working on Windows, byt maybe Windows is using another method for autodetection.

    – Jorge Suárez de Lis
    Sep 12 '13 at 12:35











  • I don't have another monitor :(

    – Joren
    Sep 12 '13 at 12:36














7












7








7


3






When I disconnect my monitor from my laptop, Ubuntu still seems to think that it is plugged in and does't update the display. This issue is Ubuntu specific (not occuring in windows) and my monitor worked fine with another laptop (Ubuntu 13.04, exact same drivers).



The quickfix:




  • open system settings

  • click Displays


Useful specs:





  • Graphics drivers: nvidia-313 (problem also occurs with the other propriatary drivers)


  • Graphics card: Nvidia Quadro K1000M


  • Monitor: Benq ET-0019-N


  • Cable: VGA D-sub DE15


  • OS: Ubuntu 13.04




I would like Ubuntu to update the display settings automagically whenever the monitor cable gets disconnected. How would I do that?










share|improve this question
















When I disconnect my monitor from my laptop, Ubuntu still seems to think that it is plugged in and does't update the display. This issue is Ubuntu specific (not occuring in windows) and my monitor worked fine with another laptop (Ubuntu 13.04, exact same drivers).



The quickfix:




  • open system settings

  • click Displays


Useful specs:





  • Graphics drivers: nvidia-313 (problem also occurs with the other propriatary drivers)


  • Graphics card: Nvidia Quadro K1000M


  • Monitor: Benq ET-0019-N


  • Cable: VGA D-sub DE15


  • OS: Ubuntu 13.04




I would like Ubuntu to update the display settings automagically whenever the monitor cable gets disconnected. How would I do that?







13.04 nvidia multiple-monitors display






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 9 '13 at 10:41







Joren

















asked Aug 22 '13 at 20:05









JorenJoren

3,58163151




3,58163151













  • What monitor is it? Some older monitors don't send any signal so the computer doesn't know whether it's there, but I don't think there are many left in service. Also what exact model of graphics card do you have, and are you using the proprietary driver or the free driver?

    – Gilles
    Aug 22 '13 at 20:30











  • I've edited my question to answer yours.

    – Joren
    Aug 22 '13 at 20:42











  • The display settings are updated when you start the computer without the cable, and then attach it? If not, are they updated when you issue the command xrandr manually?

    – Jorge Suárez de Lis
    Sep 9 '13 at 9:58











  • Can't you try another monitor and cable? I know that it's working on Windows, byt maybe Windows is using another method for autodetection.

    – Jorge Suárez de Lis
    Sep 12 '13 at 12:35











  • I don't have another monitor :(

    – Joren
    Sep 12 '13 at 12:36



















  • What monitor is it? Some older monitors don't send any signal so the computer doesn't know whether it's there, but I don't think there are many left in service. Also what exact model of graphics card do you have, and are you using the proprietary driver or the free driver?

    – Gilles
    Aug 22 '13 at 20:30











  • I've edited my question to answer yours.

    – Joren
    Aug 22 '13 at 20:42











  • The display settings are updated when you start the computer without the cable, and then attach it? If not, are they updated when you issue the command xrandr manually?

    – Jorge Suárez de Lis
    Sep 9 '13 at 9:58











  • Can't you try another monitor and cable? I know that it's working on Windows, byt maybe Windows is using another method for autodetection.

    – Jorge Suárez de Lis
    Sep 12 '13 at 12:35











  • I don't have another monitor :(

    – Joren
    Sep 12 '13 at 12:36

















What monitor is it? Some older monitors don't send any signal so the computer doesn't know whether it's there, but I don't think there are many left in service. Also what exact model of graphics card do you have, and are you using the proprietary driver or the free driver?

– Gilles
Aug 22 '13 at 20:30





What monitor is it? Some older monitors don't send any signal so the computer doesn't know whether it's there, but I don't think there are many left in service. Also what exact model of graphics card do you have, and are you using the proprietary driver or the free driver?

– Gilles
Aug 22 '13 at 20:30













I've edited my question to answer yours.

– Joren
Aug 22 '13 at 20:42





I've edited my question to answer yours.

– Joren
Aug 22 '13 at 20:42













The display settings are updated when you start the computer without the cable, and then attach it? If not, are they updated when you issue the command xrandr manually?

– Jorge Suárez de Lis
Sep 9 '13 at 9:58





The display settings are updated when you start the computer without the cable, and then attach it? If not, are they updated when you issue the command xrandr manually?

– Jorge Suárez de Lis
Sep 9 '13 at 9:58













Can't you try another monitor and cable? I know that it's working on Windows, byt maybe Windows is using another method for autodetection.

– Jorge Suárez de Lis
Sep 12 '13 at 12:35





Can't you try another monitor and cable? I know that it's working on Windows, byt maybe Windows is using another method for autodetection.

– Jorge Suárez de Lis
Sep 12 '13 at 12:35













I don't have another monitor :(

– Joren
Sep 12 '13 at 12:36





I don't have another monitor :(

– Joren
Sep 12 '13 at 12:36










3 Answers
3






active

oldest

votes


















2





+100









There is an old bug on Launchpad - bug #306735 - which was marked invalid, the explanation being that it is a known problem but fairly complex (more explanation here).



So, as far as I know, there is not an automatic method for what you asked in the true sense. But you can use autorandr (you have to install disper first - run sudo apt-get install disper from terminal), a script by Stefan Tomanek. Using this script (autorandr) you can add a keyboard shortcut for autorandr --change command and all you have to do when you connect or disconnect an external monitor is to press that keyboard shortcut. All of these are explained very nice in this answer (I just tested in Ubuntu 13.04 and everything goes well).



After you test the script in terminal, you must to see the following post if you want to add a custom keyboard shortcut for the script:




  • How can I change what keys on my keyboard do? (How can I create custom keyboard commands/shortcuts?)






share|improve this answer


























  • I had disper already installed but autorand wasn't found

    – Joren
    Sep 14 '13 at 10:00











  • @Joren What do you mean by was'n found? It is a script at the given link in the answer. Do you need help about how to use or run it?

    – Radu Rădeanu
    Sep 14 '13 at 11:05













  • Oh nevermind, I thought it came automagically with disper

    – Joren
    Sep 14 '13 at 11:15











  • @Joren No, it doesn't (I thought that my answer was clear). You have to manually create a file script named autorandr or autodisper, put inside all the text from here exactly as it is and save it in your ~/bin directory. Don't forget to make it executable with: chmod +x ~/bin/autorandr (or chmod +x ~/bin/autodisper) and then just run autorandr --help (or autodisper --help) for further help.

    – Radu Rădeanu
    Sep 14 '13 at 11:40






  • 1





    I still had this problem using 16.04! =/ The disper is still around but I had to run something like disper -e and everything got back to work, even the Display application.

    – Nigini
    Dec 7 '16 at 20:13





















1














From the Appendix B in the NVIDIA driver README:




Option "UseHotplugEvents" "boolean"


When this option is enabled, the NVIDIA X driver will generate RandR display changed events when displays are plugged into or
unplugged from an NVIDIA GPU. Some desktop environments will listen
for these events and dynamically reconfigure the desktop when displays
are added or removed.



Disabling this option suppresses the generation of these RandR events for non-DisplayPort displays, i.e., ones connected via VGA,
DVI, or HDMI. Hotplug events cannot be suppressed for displays
connected via DisplayPort.



Note that probing the display configuration (e.g. with xrandr or nvidia-settings) may cause RandR display changed events to be
generated, regardless of whether this option is enabled or disabled.
Additionally, some VGA ports are incapable of hotplug detection: on
such ports, the addition or removal of displays can only be detected
by re-probing the display configuration.



Default: on. The driver will generate RandR events when displays are added or removed.




So, assuming you have not disabled this option, the problem narrows to one of these alternatives:




  • The VGA cable or the VGA connector on the card have some DDC pins broken (either pin 12, pin 15 or pin 9). Please attach another VGA cable and try again.


  • Your Nvidia Quadro K1000M based video card has a connector that does NOT support this detection, and invoking xrandr or equivalents (as opening the Display Settings) fire this detection. If that is the case, this will never work --but the detection shouldn't work either on other Operative Systems. Never seen this in person, though.


  • Or maybe there is some bug on the NVIDIA driver that prevents this detection from working properly. Try another driver versions (such as 304) and see if the problem persists.






share
























  • Thank you for your answer, but as I stated in my question: The issue does not occur when I boot my machine in Windows. So we can exclude the first two alternatives. I've also tried the third alternative and it didn't work.

    – Joren
    Sep 9 '13 at 10:43











  • Ok. This isn't a valid answer, but to try to help you: while you wait for an answer, ask also on the NVIDIA Linux forum.

    – Jorge Suárez de Lis
    Sep 9 '13 at 14:19











  • Thank you for the suggestion. (devtalk.nvidia.com/default/topic/606465/linux/…)

    – Joren
    Sep 9 '13 at 14:41



















0














If you are running some flavour of nvidia's proprietary driver, then, as mentioned in Jorge's answer, just running xrandr on its own seems to fix the issue.





share























    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


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f335992%2fnot-updating-display-settings-when-disconnecting-external-monitor%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2





    +100









    There is an old bug on Launchpad - bug #306735 - which was marked invalid, the explanation being that it is a known problem but fairly complex (more explanation here).



    So, as far as I know, there is not an automatic method for what you asked in the true sense. But you can use autorandr (you have to install disper first - run sudo apt-get install disper from terminal), a script by Stefan Tomanek. Using this script (autorandr) you can add a keyboard shortcut for autorandr --change command and all you have to do when you connect or disconnect an external monitor is to press that keyboard shortcut. All of these are explained very nice in this answer (I just tested in Ubuntu 13.04 and everything goes well).



    After you test the script in terminal, you must to see the following post if you want to add a custom keyboard shortcut for the script:




    • How can I change what keys on my keyboard do? (How can I create custom keyboard commands/shortcuts?)






    share|improve this answer


























    • I had disper already installed but autorand wasn't found

      – Joren
      Sep 14 '13 at 10:00











    • @Joren What do you mean by was'n found? It is a script at the given link in the answer. Do you need help about how to use or run it?

      – Radu Rădeanu
      Sep 14 '13 at 11:05













    • Oh nevermind, I thought it came automagically with disper

      – Joren
      Sep 14 '13 at 11:15











    • @Joren No, it doesn't (I thought that my answer was clear). You have to manually create a file script named autorandr or autodisper, put inside all the text from here exactly as it is and save it in your ~/bin directory. Don't forget to make it executable with: chmod +x ~/bin/autorandr (or chmod +x ~/bin/autodisper) and then just run autorandr --help (or autodisper --help) for further help.

      – Radu Rădeanu
      Sep 14 '13 at 11:40






    • 1





      I still had this problem using 16.04! =/ The disper is still around but I had to run something like disper -e and everything got back to work, even the Display application.

      – Nigini
      Dec 7 '16 at 20:13


















    2





    +100









    There is an old bug on Launchpad - bug #306735 - which was marked invalid, the explanation being that it is a known problem but fairly complex (more explanation here).



    So, as far as I know, there is not an automatic method for what you asked in the true sense. But you can use autorandr (you have to install disper first - run sudo apt-get install disper from terminal), a script by Stefan Tomanek. Using this script (autorandr) you can add a keyboard shortcut for autorandr --change command and all you have to do when you connect or disconnect an external monitor is to press that keyboard shortcut. All of these are explained very nice in this answer (I just tested in Ubuntu 13.04 and everything goes well).



    After you test the script in terminal, you must to see the following post if you want to add a custom keyboard shortcut for the script:




    • How can I change what keys on my keyboard do? (How can I create custom keyboard commands/shortcuts?)






    share|improve this answer


























    • I had disper already installed but autorand wasn't found

      – Joren
      Sep 14 '13 at 10:00











    • @Joren What do you mean by was'n found? It is a script at the given link in the answer. Do you need help about how to use or run it?

      – Radu Rădeanu
      Sep 14 '13 at 11:05













    • Oh nevermind, I thought it came automagically with disper

      – Joren
      Sep 14 '13 at 11:15











    • @Joren No, it doesn't (I thought that my answer was clear). You have to manually create a file script named autorandr or autodisper, put inside all the text from here exactly as it is and save it in your ~/bin directory. Don't forget to make it executable with: chmod +x ~/bin/autorandr (or chmod +x ~/bin/autodisper) and then just run autorandr --help (or autodisper --help) for further help.

      – Radu Rădeanu
      Sep 14 '13 at 11:40






    • 1





      I still had this problem using 16.04! =/ The disper is still around but I had to run something like disper -e and everything got back to work, even the Display application.

      – Nigini
      Dec 7 '16 at 20:13
















    2





    +100







    2





    +100



    2




    +100





    There is an old bug on Launchpad - bug #306735 - which was marked invalid, the explanation being that it is a known problem but fairly complex (more explanation here).



    So, as far as I know, there is not an automatic method for what you asked in the true sense. But you can use autorandr (you have to install disper first - run sudo apt-get install disper from terminal), a script by Stefan Tomanek. Using this script (autorandr) you can add a keyboard shortcut for autorandr --change command and all you have to do when you connect or disconnect an external monitor is to press that keyboard shortcut. All of these are explained very nice in this answer (I just tested in Ubuntu 13.04 and everything goes well).



    After you test the script in terminal, you must to see the following post if you want to add a custom keyboard shortcut for the script:




    • How can I change what keys on my keyboard do? (How can I create custom keyboard commands/shortcuts?)






    share|improve this answer















    There is an old bug on Launchpad - bug #306735 - which was marked invalid, the explanation being that it is a known problem but fairly complex (more explanation here).



    So, as far as I know, there is not an automatic method for what you asked in the true sense. But you can use autorandr (you have to install disper first - run sudo apt-get install disper from terminal), a script by Stefan Tomanek. Using this script (autorandr) you can add a keyboard shortcut for autorandr --change command and all you have to do when you connect or disconnect an external monitor is to press that keyboard shortcut. All of these are explained very nice in this answer (I just tested in Ubuntu 13.04 and everything goes well).



    After you test the script in terminal, you must to see the following post if you want to add a custom keyboard shortcut for the script:




    • How can I change what keys on my keyboard do? (How can I create custom keyboard commands/shortcuts?)







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 13 '17 at 12:23









    Community

    1




    1










    answered Sep 14 '13 at 8:07









    Radu RădeanuRadu Rădeanu

    119k35252328




    119k35252328













    • I had disper already installed but autorand wasn't found

      – Joren
      Sep 14 '13 at 10:00











    • @Joren What do you mean by was'n found? It is a script at the given link in the answer. Do you need help about how to use or run it?

      – Radu Rădeanu
      Sep 14 '13 at 11:05













    • Oh nevermind, I thought it came automagically with disper

      – Joren
      Sep 14 '13 at 11:15











    • @Joren No, it doesn't (I thought that my answer was clear). You have to manually create a file script named autorandr or autodisper, put inside all the text from here exactly as it is and save it in your ~/bin directory. Don't forget to make it executable with: chmod +x ~/bin/autorandr (or chmod +x ~/bin/autodisper) and then just run autorandr --help (or autodisper --help) for further help.

      – Radu Rădeanu
      Sep 14 '13 at 11:40






    • 1





      I still had this problem using 16.04! =/ The disper is still around but I had to run something like disper -e and everything got back to work, even the Display application.

      – Nigini
      Dec 7 '16 at 20:13





















    • I had disper already installed but autorand wasn't found

      – Joren
      Sep 14 '13 at 10:00











    • @Joren What do you mean by was'n found? It is a script at the given link in the answer. Do you need help about how to use or run it?

      – Radu Rădeanu
      Sep 14 '13 at 11:05













    • Oh nevermind, I thought it came automagically with disper

      – Joren
      Sep 14 '13 at 11:15











    • @Joren No, it doesn't (I thought that my answer was clear). You have to manually create a file script named autorandr or autodisper, put inside all the text from here exactly as it is and save it in your ~/bin directory. Don't forget to make it executable with: chmod +x ~/bin/autorandr (or chmod +x ~/bin/autodisper) and then just run autorandr --help (or autodisper --help) for further help.

      – Radu Rădeanu
      Sep 14 '13 at 11:40






    • 1





      I still had this problem using 16.04! =/ The disper is still around but I had to run something like disper -e and everything got back to work, even the Display application.

      – Nigini
      Dec 7 '16 at 20:13



















    I had disper already installed but autorand wasn't found

    – Joren
    Sep 14 '13 at 10:00





    I had disper already installed but autorand wasn't found

    – Joren
    Sep 14 '13 at 10:00













    @Joren What do you mean by was'n found? It is a script at the given link in the answer. Do you need help about how to use or run it?

    – Radu Rădeanu
    Sep 14 '13 at 11:05







    @Joren What do you mean by was'n found? It is a script at the given link in the answer. Do you need help about how to use or run it?

    – Radu Rădeanu
    Sep 14 '13 at 11:05















    Oh nevermind, I thought it came automagically with disper

    – Joren
    Sep 14 '13 at 11:15





    Oh nevermind, I thought it came automagically with disper

    – Joren
    Sep 14 '13 at 11:15













    @Joren No, it doesn't (I thought that my answer was clear). You have to manually create a file script named autorandr or autodisper, put inside all the text from here exactly as it is and save it in your ~/bin directory. Don't forget to make it executable with: chmod +x ~/bin/autorandr (or chmod +x ~/bin/autodisper) and then just run autorandr --help (or autodisper --help) for further help.

    – Radu Rădeanu
    Sep 14 '13 at 11:40





    @Joren No, it doesn't (I thought that my answer was clear). You have to manually create a file script named autorandr or autodisper, put inside all the text from here exactly as it is and save it in your ~/bin directory. Don't forget to make it executable with: chmod +x ~/bin/autorandr (or chmod +x ~/bin/autodisper) and then just run autorandr --help (or autodisper --help) for further help.

    – Radu Rădeanu
    Sep 14 '13 at 11:40




    1




    1





    I still had this problem using 16.04! =/ The disper is still around but I had to run something like disper -e and everything got back to work, even the Display application.

    – Nigini
    Dec 7 '16 at 20:13







    I still had this problem using 16.04! =/ The disper is still around but I had to run something like disper -e and everything got back to work, even the Display application.

    – Nigini
    Dec 7 '16 at 20:13















    1














    From the Appendix B in the NVIDIA driver README:




    Option "UseHotplugEvents" "boolean"


    When this option is enabled, the NVIDIA X driver will generate RandR display changed events when displays are plugged into or
    unplugged from an NVIDIA GPU. Some desktop environments will listen
    for these events and dynamically reconfigure the desktop when displays
    are added or removed.



    Disabling this option suppresses the generation of these RandR events for non-DisplayPort displays, i.e., ones connected via VGA,
    DVI, or HDMI. Hotplug events cannot be suppressed for displays
    connected via DisplayPort.



    Note that probing the display configuration (e.g. with xrandr or nvidia-settings) may cause RandR display changed events to be
    generated, regardless of whether this option is enabled or disabled.
    Additionally, some VGA ports are incapable of hotplug detection: on
    such ports, the addition or removal of displays can only be detected
    by re-probing the display configuration.



    Default: on. The driver will generate RandR events when displays are added or removed.




    So, assuming you have not disabled this option, the problem narrows to one of these alternatives:




    • The VGA cable or the VGA connector on the card have some DDC pins broken (either pin 12, pin 15 or pin 9). Please attach another VGA cable and try again.


    • Your Nvidia Quadro K1000M based video card has a connector that does NOT support this detection, and invoking xrandr or equivalents (as opening the Display Settings) fire this detection. If that is the case, this will never work --but the detection shouldn't work either on other Operative Systems. Never seen this in person, though.


    • Or maybe there is some bug on the NVIDIA driver that prevents this detection from working properly. Try another driver versions (such as 304) and see if the problem persists.






    share
























    • Thank you for your answer, but as I stated in my question: The issue does not occur when I boot my machine in Windows. So we can exclude the first two alternatives. I've also tried the third alternative and it didn't work.

      – Joren
      Sep 9 '13 at 10:43











    • Ok. This isn't a valid answer, but to try to help you: while you wait for an answer, ask also on the NVIDIA Linux forum.

      – Jorge Suárez de Lis
      Sep 9 '13 at 14:19











    • Thank you for the suggestion. (devtalk.nvidia.com/default/topic/606465/linux/…)

      – Joren
      Sep 9 '13 at 14:41
















    1














    From the Appendix B in the NVIDIA driver README:




    Option "UseHotplugEvents" "boolean"


    When this option is enabled, the NVIDIA X driver will generate RandR display changed events when displays are plugged into or
    unplugged from an NVIDIA GPU. Some desktop environments will listen
    for these events and dynamically reconfigure the desktop when displays
    are added or removed.



    Disabling this option suppresses the generation of these RandR events for non-DisplayPort displays, i.e., ones connected via VGA,
    DVI, or HDMI. Hotplug events cannot be suppressed for displays
    connected via DisplayPort.



    Note that probing the display configuration (e.g. with xrandr or nvidia-settings) may cause RandR display changed events to be
    generated, regardless of whether this option is enabled or disabled.
    Additionally, some VGA ports are incapable of hotplug detection: on
    such ports, the addition or removal of displays can only be detected
    by re-probing the display configuration.



    Default: on. The driver will generate RandR events when displays are added or removed.




    So, assuming you have not disabled this option, the problem narrows to one of these alternatives:




    • The VGA cable or the VGA connector on the card have some DDC pins broken (either pin 12, pin 15 or pin 9). Please attach another VGA cable and try again.


    • Your Nvidia Quadro K1000M based video card has a connector that does NOT support this detection, and invoking xrandr or equivalents (as opening the Display Settings) fire this detection. If that is the case, this will never work --but the detection shouldn't work either on other Operative Systems. Never seen this in person, though.


    • Or maybe there is some bug on the NVIDIA driver that prevents this detection from working properly. Try another driver versions (such as 304) and see if the problem persists.






    share
























    • Thank you for your answer, but as I stated in my question: The issue does not occur when I boot my machine in Windows. So we can exclude the first two alternatives. I've also tried the third alternative and it didn't work.

      – Joren
      Sep 9 '13 at 10:43











    • Ok. This isn't a valid answer, but to try to help you: while you wait for an answer, ask also on the NVIDIA Linux forum.

      – Jorge Suárez de Lis
      Sep 9 '13 at 14:19











    • Thank you for the suggestion. (devtalk.nvidia.com/default/topic/606465/linux/…)

      – Joren
      Sep 9 '13 at 14:41














    1












    1








    1







    From the Appendix B in the NVIDIA driver README:




    Option "UseHotplugEvents" "boolean"


    When this option is enabled, the NVIDIA X driver will generate RandR display changed events when displays are plugged into or
    unplugged from an NVIDIA GPU. Some desktop environments will listen
    for these events and dynamically reconfigure the desktop when displays
    are added or removed.



    Disabling this option suppresses the generation of these RandR events for non-DisplayPort displays, i.e., ones connected via VGA,
    DVI, or HDMI. Hotplug events cannot be suppressed for displays
    connected via DisplayPort.



    Note that probing the display configuration (e.g. with xrandr or nvidia-settings) may cause RandR display changed events to be
    generated, regardless of whether this option is enabled or disabled.
    Additionally, some VGA ports are incapable of hotplug detection: on
    such ports, the addition or removal of displays can only be detected
    by re-probing the display configuration.



    Default: on. The driver will generate RandR events when displays are added or removed.




    So, assuming you have not disabled this option, the problem narrows to one of these alternatives:




    • The VGA cable or the VGA connector on the card have some DDC pins broken (either pin 12, pin 15 or pin 9). Please attach another VGA cable and try again.


    • Your Nvidia Quadro K1000M based video card has a connector that does NOT support this detection, and invoking xrandr or equivalents (as opening the Display Settings) fire this detection. If that is the case, this will never work --but the detection shouldn't work either on other Operative Systems. Never seen this in person, though.


    • Or maybe there is some bug on the NVIDIA driver that prevents this detection from working properly. Try another driver versions (such as 304) and see if the problem persists.






    share













    From the Appendix B in the NVIDIA driver README:




    Option "UseHotplugEvents" "boolean"


    When this option is enabled, the NVIDIA X driver will generate RandR display changed events when displays are plugged into or
    unplugged from an NVIDIA GPU. Some desktop environments will listen
    for these events and dynamically reconfigure the desktop when displays
    are added or removed.



    Disabling this option suppresses the generation of these RandR events for non-DisplayPort displays, i.e., ones connected via VGA,
    DVI, or HDMI. Hotplug events cannot be suppressed for displays
    connected via DisplayPort.



    Note that probing the display configuration (e.g. with xrandr or nvidia-settings) may cause RandR display changed events to be
    generated, regardless of whether this option is enabled or disabled.
    Additionally, some VGA ports are incapable of hotplug detection: on
    such ports, the addition or removal of displays can only be detected
    by re-probing the display configuration.



    Default: on. The driver will generate RandR events when displays are added or removed.




    So, assuming you have not disabled this option, the problem narrows to one of these alternatives:




    • The VGA cable or the VGA connector on the card have some DDC pins broken (either pin 12, pin 15 or pin 9). Please attach another VGA cable and try again.


    • Your Nvidia Quadro K1000M based video card has a connector that does NOT support this detection, and invoking xrandr or equivalents (as opening the Display Settings) fire this detection. If that is the case, this will never work --but the detection shouldn't work either on other Operative Systems. Never seen this in person, though.


    • Or maybe there is some bug on the NVIDIA driver that prevents this detection from working properly. Try another driver versions (such as 304) and see if the problem persists.







    share











    share


    share










    answered Sep 9 '13 at 10:22









    Jorge Suárez de LisJorge Suárez de Lis

    1,72121231




    1,72121231













    • Thank you for your answer, but as I stated in my question: The issue does not occur when I boot my machine in Windows. So we can exclude the first two alternatives. I've also tried the third alternative and it didn't work.

      – Joren
      Sep 9 '13 at 10:43











    • Ok. This isn't a valid answer, but to try to help you: while you wait for an answer, ask also on the NVIDIA Linux forum.

      – Jorge Suárez de Lis
      Sep 9 '13 at 14:19











    • Thank you for the suggestion. (devtalk.nvidia.com/default/topic/606465/linux/…)

      – Joren
      Sep 9 '13 at 14:41



















    • Thank you for your answer, but as I stated in my question: The issue does not occur when I boot my machine in Windows. So we can exclude the first two alternatives. I've also tried the third alternative and it didn't work.

      – Joren
      Sep 9 '13 at 10:43











    • Ok. This isn't a valid answer, but to try to help you: while you wait for an answer, ask also on the NVIDIA Linux forum.

      – Jorge Suárez de Lis
      Sep 9 '13 at 14:19











    • Thank you for the suggestion. (devtalk.nvidia.com/default/topic/606465/linux/…)

      – Joren
      Sep 9 '13 at 14:41

















    Thank you for your answer, but as I stated in my question: The issue does not occur when I boot my machine in Windows. So we can exclude the first two alternatives. I've also tried the third alternative and it didn't work.

    – Joren
    Sep 9 '13 at 10:43





    Thank you for your answer, but as I stated in my question: The issue does not occur when I boot my machine in Windows. So we can exclude the first two alternatives. I've also tried the third alternative and it didn't work.

    – Joren
    Sep 9 '13 at 10:43













    Ok. This isn't a valid answer, but to try to help you: while you wait for an answer, ask also on the NVIDIA Linux forum.

    – Jorge Suárez de Lis
    Sep 9 '13 at 14:19





    Ok. This isn't a valid answer, but to try to help you: while you wait for an answer, ask also on the NVIDIA Linux forum.

    – Jorge Suárez de Lis
    Sep 9 '13 at 14:19













    Thank you for the suggestion. (devtalk.nvidia.com/default/topic/606465/linux/…)

    – Joren
    Sep 9 '13 at 14:41





    Thank you for the suggestion. (devtalk.nvidia.com/default/topic/606465/linux/…)

    – Joren
    Sep 9 '13 at 14:41











    0














    If you are running some flavour of nvidia's proprietary driver, then, as mentioned in Jorge's answer, just running xrandr on its own seems to fix the issue.





    share




























      0














      If you are running some flavour of nvidia's proprietary driver, then, as mentioned in Jorge's answer, just running xrandr on its own seems to fix the issue.





      share


























        0












        0








        0







        If you are running some flavour of nvidia's proprietary driver, then, as mentioned in Jorge's answer, just running xrandr on its own seems to fix the issue.





        share













        If you are running some flavour of nvidia's proprietary driver, then, as mentioned in Jorge's answer, just running xrandr on its own seems to fix the issue.






        share











        share


        share










        answered 8 mins ago









        ccpizzaccpizza

        869912




        869912






























            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














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f335992%2fnot-updating-display-settings-when-disconnecting-external-monitor%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...