From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71461] monitor doesn't get detected after boot or disconnection
Date: Wed, 09 Apr 2014 06:10:47 +0000 [thread overview]
Message-ID: <bug-71461-2300-yRyVV7Xq0Q@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71461-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #24 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Tom Yan from comment #22)
> Do you have any case that the code would do something positive? Or
> ultimately, would you consider removing the code upstream?
It works for the vast majority of users and removing it would break unplug and
replug of DP displays. Without that code you would have to manually disable
and re-enable the display using xrandr every time you connect or disconnect a
DP display. It would also break disconnect and reconnect of dp displays for
the console.
In your case we need to find out why it's not working properly for you. You
mentioned that it works properly in the console but not in X. That sounds like
maybe your desktop environment is trying to do something special which causes
the problem. Does it work properly with a bare X server? E.g., just run Xorg
without a desktop environment.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-04-09 6:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 8:06 [Bug 71461] New: monitor doesn't get detected after boot bugzilla-daemon
2014-03-03 12:45 ` [Bug 71461] monitor doesn't get detected after boot or disconnection bugzilla-daemon
2014-03-03 12:47 ` bugzilla-daemon
2014-03-03 14:54 ` bugzilla-daemon
2014-03-03 15:22 ` bugzilla-daemon
2014-03-03 15:23 ` bugzilla-daemon
2014-03-03 15:25 ` bugzilla-daemon
2014-03-03 15:36 ` bugzilla-daemon
2014-03-03 15:41 ` bugzilla-daemon
2014-03-03 15:43 ` bugzilla-daemon
2014-03-03 17:16 ` bugzilla-daemon
2014-03-03 17:25 ` bugzilla-daemon
2014-03-11 17:07 ` bugzilla-daemon
2014-03-11 18:14 ` bugzilla-daemon
2014-03-12 17:10 ` bugzilla-daemon
2014-03-23 20:34 ` bugzilla-daemon
2014-03-23 20:54 ` bugzilla-daemon
2014-04-07 18:21 ` bugzilla-daemon
2014-04-07 18:41 ` bugzilla-daemon
2014-04-07 19:26 ` bugzilla-daemon
2014-04-08 17:16 ` bugzilla-daemon
2014-04-08 18:47 ` bugzilla-daemon
2014-04-08 19:15 ` bugzilla-daemon
2014-04-09 6:00 ` bugzilla-daemon
2014-04-09 6:10 ` bugzilla-daemon
2014-04-09 6:10 ` bugzilla-daemon [this message]
2014-04-09 6:12 ` bugzilla-daemon
2014-04-09 7:01 ` bugzilla-daemon
2014-04-09 7:07 ` bugzilla-daemon
2014-04-09 18:40 ` bugzilla-daemon
2014-04-09 18:53 ` bugzilla-daemon
2014-04-09 20:00 ` bugzilla-daemon
2014-04-12 2:14 ` bugzilla-daemon
2014-04-12 2:44 ` bugzilla-daemon
2015-10-30 23:34 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-71461-2300-yRyVV7Xq0Q@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.