Sfdwhf

Is it possible to run Internet Explorer on OS X El Capitan?

How to move a thin line with the black arrow in Illustrator?

Why does Kotter return in Welcome Back Kotter?

Does detail obscure or enhance action?

How much RAM could one put in a typical 80386 setup?

Is it legal for company to use my work email to pretend I still work there?

What does "Puller Prush Person" mean?

DC-DC converter from low voltage at high current, to high voltage at low current

Is it unprofessional to ask if a job posting on GlassDoor is real?

Why doesn't H₄O²⁺ exist?

Why is consensus so controversial in Britain?

Mortgage Pre-approval / Loan - Apply Alone or with Fiancée?

How does quantile regression compare to logistic regression with the variable split at the quantile?

What's that red-plus icon near a text?

Revoked SSL certificate

expand `ifthenelse` immediately

Can a vampire attack twice with their claws using Multiattack?

Replacing matching entries in one column of a file by another column from a different file

Can a monk's single staff be considered dual wielded, as per the Dual Wielder feat?

How to determine what difficulty is right for the game?

Modeling an IP Address

Alternative to sending password over mail?

What typically incentivizes a professor to change jobs to a lower ranking university?

Do I have a twin with permutated remainders?

Ubuntu 17.10: One of the two DisplayPort monitors connected to my PC does not wake up from suspend

Dell E6510 with Intel i950 cannot detect second display in PreciseHow to make “xrandr” work with GMA500?HP Spectre x360 does not wake up from suspend correctly after upgrade to 17.10Problem with waking from suspend to RAM on 17.10ACPI Error: Method parse/execution failed; NVRM: Xid: 79, GPU has fallen off the busResume from suspend - Ubuntu 17.10Ubuntu 17.10 Suspend not resumingUbuntu won't wake up from suspendXfce4 multi-graphic-card and multi-monitor: placement of desktop iconsWake from suspend issues

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

1

If I set "Blank screen" in "Power Saving" settings to anything other than "Never":

When the displays go blank and I come back the day after to use my PC, one of the displays remains blank and I have to restart the computer to make it work again.

Here are the display settings:

$ xrandr --verbose

Screen 0: minimum 320 x 200, current 5120 x 1440, maximum 8192 x 8192

XWAYLAND0 connected 2560x1440+0+0 (0x24) normal (normal left inverted right x axis y axis) 600mm x 340mm

    Identifier: 0x21

    Timestamp:  221264

    Subpixel:   unknown

    Gamma:      1.0:1.0:1.0

    Brightness: 0.0

    Clones:    

    CRTC:       0

    CRTCs:      0

    Transform:  1.000000 0.000000 0.000000

                0.000000 1.000000 0.000000

                0.000000 0.000000 1.000000

               filter: 

  2560x1440 (0x24) 312.000MHz -HSync +VSync *current +preferred

        h: width  2560 start 2752 end 3024 total 3488 skew    0 clock  89.45KHz

        v: height 1440 start 1443 end 1448 total 1493           clock  59.91Hz

XWAYLAND1 connected 2560x1440+2560+0 (0x24) normal (normal left inverted right x axis y axis) 600mm x 340mm

    Identifier: 0x23

    Timestamp:  221264

    Subpixel:   unknown

    Gamma:      1.0:1.0:1.0

    Brightness: 0.0

    Clones:    

    CRTC:       1

    CRTCs:      1

    Transform:  1.000000 0.000000 0.000000

                0.000000 1.000000 0.000000

                0.000000 0.000000 1.000000

               filter: 

  2560x1440 (0x24) 312.000MHz -HSync +VSync *current +preferred

        h: width  2560 start 2752 end 3024 total 3488 skew    0 clock  89.45KHz

        v: height 1440 start 1443 end 1448 total 1493           clock  59.91Hz

How can I fix this issue?

multiple-monitors suspend power-management 17.10

share|improve this question

asked Nov 11 '17 at 7:20

BehrangBehrang

322215

add a comment | 

1

If I set "Blank screen" in "Power Saving" settings to anything other than "Never":

When the displays go blank and I come back the day after to use my PC, one of the displays remains blank and I have to restart the computer to make it work again.

Here are the display settings:

$ xrandr --verbose

Screen 0: minimum 320 x 200, current 5120 x 1440, maximum 8192 x 8192

XWAYLAND0 connected 2560x1440+0+0 (0x24) normal (normal left inverted right x axis y axis) 600mm x 340mm

    Identifier: 0x21

    Timestamp:  221264

    Subpixel:   unknown

    Gamma:      1.0:1.0:1.0

    Brightness: 0.0

    Clones:    

    CRTC:       0

    CRTCs:      0

    Transform:  1.000000 0.000000 0.000000

                0.000000 1.000000 0.000000

                0.000000 0.000000 1.000000

               filter: 

  2560x1440 (0x24) 312.000MHz -HSync +VSync *current +preferred

        h: width  2560 start 2752 end 3024 total 3488 skew    0 clock  89.45KHz

        v: height 1440 start 1443 end 1448 total 1493           clock  59.91Hz

XWAYLAND1 connected 2560x1440+2560+0 (0x24) normal (normal left inverted right x axis y axis) 600mm x 340mm

    Identifier: 0x23

    Timestamp:  221264

    Subpixel:   unknown

    Gamma:      1.0:1.0:1.0

    Brightness: 0.0

    Clones:    

    CRTC:       1

    CRTCs:      1

    Transform:  1.000000 0.000000 0.000000

                0.000000 1.000000 0.000000

                0.000000 0.000000 1.000000

               filter: 

  2560x1440 (0x24) 312.000MHz -HSync +VSync *current +preferred

        h: width  2560 start 2752 end 3024 total 3488 skew    0 clock  89.45KHz

        v: height 1440 start 1443 end 1448 total 1493           clock  59.91Hz

How can I fix this issue?

multiple-monitors suspend power-management 17.10

share|improve this question

asked Nov 11 '17 at 7:20

BehrangBehrang

322215

add a comment | 

If I set "Blank screen" in "Power Saving" settings to anything other than "Never":

When the displays go blank and I come back the day after to use my PC, one of the displays remains blank and I have to restart the computer to make it work again.

Here are the display settings:

$ xrandr --verbose

Screen 0: minimum 320 x 200, current 5120 x 1440, maximum 8192 x 8192

XWAYLAND0 connected 2560x1440+0+0 (0x24) normal (normal left inverted right x axis y axis) 600mm x 340mm

    Identifier: 0x21

    Timestamp:  221264

    Subpixel:   unknown

    Gamma:      1.0:1.0:1.0

    Brightness: 0.0

    Clones:    

    CRTC:       0

    CRTCs:      0

    Transform:  1.000000 0.000000 0.000000

                0.000000 1.000000 0.000000

                0.000000 0.000000 1.000000

               filter: 

  2560x1440 (0x24) 312.000MHz -HSync +VSync *current +preferred

        h: width  2560 start 2752 end 3024 total 3488 skew    0 clock  89.45KHz

        v: height 1440 start 1443 end 1448 total 1493           clock  59.91Hz

XWAYLAND1 connected 2560x1440+2560+0 (0x24) normal (normal left inverted right x axis y axis) 600mm x 340mm

    Identifier: 0x23

    Timestamp:  221264

    Subpixel:   unknown

    Gamma:      1.0:1.0:1.0

    Brightness: 0.0

    Clones:    

    CRTC:       1

    CRTCs:      1

    Transform:  1.000000 0.000000 0.000000

                0.000000 1.000000 0.000000

                0.000000 0.000000 1.000000

               filter: 

  2560x1440 (0x24) 312.000MHz -HSync +VSync *current +preferred

        h: width  2560 start 2752 end 3024 total 3488 skew    0 clock  89.45KHz

        v: height 1440 start 1443 end 1448 total 1493           clock  59.91Hz

How can I fix this issue?

multiple-monitors suspend power-management 17.10

share|improve this question

asked Nov 11 '17 at 7:20

BehrangBehrang

322215

$ xrandr --verbose

Screen 0: minimum 320 x 200, current 5120 x 1440, maximum 8192 x 8192

XWAYLAND0 connected 2560x1440+0+0 (0x24) normal (normal left inverted right x axis y axis) 600mm x 340mm

    Identifier: 0x21

    Timestamp:  221264

    Subpixel:   unknown

    Gamma:      1.0:1.0:1.0

    Brightness: 0.0

    Clones:    

    CRTC:       0

    CRTCs:      0

    Transform:  1.000000 0.000000 0.000000

                0.000000 1.000000 0.000000

                0.000000 0.000000 1.000000

               filter: 

  2560x1440 (0x24) 312.000MHz -HSync +VSync *current +preferred

        h: width  2560 start 2752 end 3024 total 3488 skew    0 clock  89.45KHz

        v: height 1440 start 1443 end 1448 total 1493           clock  59.91Hz

XWAYLAND1 connected 2560x1440+2560+0 (0x24) normal (normal left inverted right x axis y axis) 600mm x 340mm

    Identifier: 0x23

    Timestamp:  221264

    Subpixel:   unknown

    Gamma:      1.0:1.0:1.0

    Brightness: 0.0

    Clones:    

    CRTC:       1

    CRTCs:      1

    Transform:  1.000000 0.000000 0.000000

                0.000000 1.000000 0.000000

                0.000000 0.000000 1.000000

               filter: 

  2560x1440 (0x24) 312.000MHz -HSync +VSync *current +preferred

        h: width  2560 start 2752 end 3024 total 3488 skew    0 clock  89.45KHz

        v: height 1440 start 1443 end 1448 total 1493           clock  59.91Hz

share|improve this question

asked Nov 11 '17 at 7:20

BehrangBehrang

322215

share|improve this question

asked Nov 11 '17 at 7:20

BehrangBehrang

322215

asked Nov 11 '17 at 7:20

BehrangBehrang

322215

asked Nov 11 '17 at 7:20

BehrangBehrang

322215

1 Answer
1

active

oldest

votes

2

Unfortunately I don't know how you can fix it but I do have an idea for a workaround that at least would prevent the need for a system reset. Mind you, this will only work if you are able to start a terminal on the monitor that does wakes up.

Let say the monitor XWAYLAND1 remains asleep.
Force it off and the on again by

xrandr --output XWAYLAND1 --off

xrandr --output XWAYLAND1 --left-of XWAYLAND0 --auto

share|improve this answer

edited 1 hour ago

Tom

276313

answered Nov 11 '17 at 20:16

user680858

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

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f975304%2fubuntu-17-10-one-of-the-two-displayport-monitors-connected-to-my-pc-does-not-wa%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

2

Unfortunately I don't know how you can fix it but I do have an idea for a workaround that at least would prevent the need for a system reset. Mind you, this will only work if you are able to start a terminal on the monitor that does wakes up.

Let say the monitor XWAYLAND1 remains asleep.
Force it off and the on again by

xrandr --output XWAYLAND1 --off

xrandr --output XWAYLAND1 --left-of XWAYLAND0 --auto

share|improve this answer

edited 1 hour ago

Tom

276313

answered Nov 11 '17 at 20:16

user680858

add a comment | 

2

Unfortunately I don't know how you can fix it but I do have an idea for a workaround that at least would prevent the need for a system reset. Mind you, this will only work if you are able to start a terminal on the monitor that does wakes up.

Let say the monitor XWAYLAND1 remains asleep.
Force it off and the on again by

xrandr --output XWAYLAND1 --off

xrandr --output XWAYLAND1 --left-of XWAYLAND0 --auto

share|improve this answer

edited 1 hour ago

Tom

276313

answered Nov 11 '17 at 20:16

user680858

add a comment | 

Unfortunately I don't know how you can fix it but I do have an idea for a workaround that at least would prevent the need for a system reset. Mind you, this will only work if you are able to start a terminal on the monitor that does wakes up.

Let say the monitor XWAYLAND1 remains asleep.
Force it off and the on again by

xrandr --output XWAYLAND1 --off

xrandr --output XWAYLAND1 --left-of XWAYLAND0 --auto

share|improve this answer

edited 1 hour ago

Tom

276313

answered Nov 11 '17 at 20:16

user680858

xrandr --output XWAYLAND1 --off

xrandr --output XWAYLAND1 --left-of XWAYLAND0 --auto

share|improve this answer

edited 1 hour ago

Tom

276313

answered Nov 11 '17 at 20:16

user680858

edited 1 hour ago

Tom

276313

edited 1 hour ago

Tom

276313