[Bug 29852] Changing external monitors requires X restart

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Aug 30 12:25:11 PDT 2010


https://bugs.freedesktop.org/show_bug.cgi?id=29852

Alex Deucher <agd5f at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |NOTOURBUG

--- Comment #15 from Alex Deucher <agd5f at yahoo.com> 2010-08-30 12:25:11 PDT ---
(In reply to comment #14)
> Thanks for the explanation, it helps me understand why this isn't done entirely
> automatically. However, because this issue has bitten me and several others I
> know, it seems like something more should be done than just me personally
> learning the properly cli incantations; for the sake of the larger community
> I'd like to see this resolved. So, can we discuss options?
> 
> 1. Automatic handling: one scenario in which it seems like randr could safely
> turn a monitor off is if one disappears AND a new one appears, and there isn't
> a free crtc. (What sets the # of crtcs? Is that a hardware thing?) In that case
> you are going to have to pick one or the other anyway, because there aren't
> enough crtcs to drive all the displays, and so you might as well go with the
> one that is connected. So to a naive person like me, automation does not really
> seem to be such a hard problem, as long as it's done only with the right
> alignment of conditions.

The number of crtcs (display controllers) is a hardware limit.  Picking the
right conditions is the hard part :)

> 
> 2. If you think instead that the logic should go in the xrandr cli tool, to
> whom should I report that? By talking to you, am I already reporting to the
> right person? :-)
> 

File a bug under Product: xorg Component: App/xrandr.

> 3. Finally, if it gets built into the xrandr cli tool, will that automatically
> cover KDE/Gnome, or do they need to work on their own implementations? I can go
> visit their bugzillas and make a report, but that would be silly if the real
> work needs to be done elsewhere anyway. Sorry to ask your help here, but I'm
> pretty naive about the architecture, and so would probably generate a lot of
> useless churn without some good guidance. Thanks for your help.

Depends on the app.  I think most use libxrandr directly, so they would
probably need similar logic.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the xorg-driver-ati mailing list