Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Monitors Aren't Detected After Login #3673

Open
zero77 opened this Issue Apr 3, 2019 · 11 comments

Comments

Projects
None yet
3 participants
@zero77
Copy link

commented Apr 3, 2019

I'm submitting a…

[x] Bug
[ ] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

When connecting or disconnecting a monitor after login i3 does not detect that it has changed.

But, if you log out and then connect or disconnect a monitor and then login again, it all works fine, but not whilst logged in.

Expected Behavior

When connecting a monitor the new monitor should be displayed.

When disconnecting a monitor it should be removed and i3 should not still try and move windows to it, or other multi monitor functionality.

Reproduction Instructions

After login, connect or disconnect a monitor and the problem occurs.

Environment

Output of i3 --moreversion 2>&-:

Binary i3 version:  4.16-124-g88912d6f (2019-03-29, branch "next") © 2009 Michael Stapelberg and contributors
Running i3 version: 4.16-124-g88912d6f (2019-03-29, branch "next") (pid 5177)
Loaded i3 config: /home/user/.config/i3/config

The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3
i3 version: 4.16-124-g88912d6f
Logfile URL: https://logs.i3wm.org/logs/5698027943624704.bz2
- Linux Distribution & Version: Ubuntu 18.04
- Are you using a compositor (e.g., xcompmgr or compton): xcompmgr v1.1.7

@i3bot i3bot added the bug label Apr 3, 2019

@i3bot

This comment has been minimized.

Copy link

commented Apr 3, 2019

I don’t see a link to logs.i3wm.org. Did you follow https://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)

@Airblader

This comment has been minimized.

Copy link
Member

commented Apr 3, 2019

When you say connect, do you mean "plug it in"? Can you check with xrandr whether the output is actually activated?

i3 doesn't manage hardware directly. We rely on RandR to notify us, so if you plug it in and nothing else takes care of activating the output in X, you need to do so yourself.

A quick test would be to run xrandr --auto to see if that picks up on the output.

@zero77

This comment has been minimized.

Copy link
Author

commented Apr 3, 2019

@Airblader

When you say connect, do you mean "plug it in"?

Yes

Can you check with xrandr whether the output is actually activated?

In terminal, xrandr detects the monitors correctly both when connected or disconnected, if thats what you mean.

A quick test would be to run xrandr --auto to see if that picks up on the output.

Yes, this works but, it changes the settings until you log out and then in again.

@Airblader

This comment has been minimized.

Copy link
Member

commented Apr 3, 2019

Can you show the output of xrandr before and after plugging the output in?

If afterwards xrandr sees the output but reports it as disconnected, you need to first activate it. Whether you do this with xrandr, arandr, udev rules etc is up to you. i3 can only use outputs once they're connected (not just plugged in).

@zero77

This comment has been minimized.

Copy link
Author

commented Apr 3, 2019

All, it shows is connected when plugged in and disconnected when plugged out, this is after logging in with the monitor plugged out.
But, even if xrandr displays as connected the monitor is not displayed.

If afterwards xrandr sees the output but reports it as disconnected, you need to first activate it.

It doesn't it seams to be working as it should but, with out displaying the monitor.

how do i test if the monitor needs activating.

@zero77

This comment has been minimized.

Copy link
Author

commented Apr 3, 2019

In terminal, xrandr seams to be working as it should i.e. displaying monitors as connected or disconnected when they actually are.

But, i3 only seams to detect monitors as connected or disconnected at the initial login point, after that it does not change regardless of whether they are displayed as connected or disconnected by xrandr.

@Airblader

This comment has been minimized.

Copy link
Member

commented Apr 3, 2019

Can you please provide the output I asked for above?

@zero77

This comment has been minimized.

Copy link
Author

commented Apr 3, 2019

Monitor Connected:
https://pastebin.com/Tj3C982L

Monitor Disconnected:
https://pastebin.com/fP5VaDHB

@Airblader

This comment has been minimized.

Copy link
Member

commented Apr 3, 2019

To clarify, the "Monitor Connected" one is from when the output was connected but i3 did not recognize it, right?

If so I think we'll need an i3 log file (see the bot's response for a link) and maybe the output of xev -event randr while plugging in the output.

@zero77

This comment has been minimized.

Copy link
Author

commented Apr 3, 2019

To clarify, the "Monitor Connected" one is from when the output was connected but i3 did not recognize it, right?

Yes

If so I think we'll need an i3 log file (see the bot's response for a link) and maybe the output of xev -event randr while plugging in the output.

Ok, i will get back to you when i have the logs

@zero77

This comment has been minimized.

Copy link
Author

commented Apr 3, 2019

@Airblader
i3 log file:
https://logs.i3wm.org/logs/5698027943624704.bz2

maybe the output of xev -event randr while plugging in the output.

What do i need to do for this.

@i3bot i3bot removed the missing-log label Apr 3, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.