[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#864166: release-notes: proofreading sweep - issues.dbk

On 06/09/2017 06:00 PM, Niels Thykier wrote:
> Julien Cristau:
>> On 06/05/2017 01:50 PM, Niels Thykier wrote:
>>> Hi,
>>> CC'ing debian-x, who I hope can help us with some clarification.
>>>  [...]
>> This looks wrong, I believe the package name is gdm3, not gdm.
> Thanks, corrected.
>> [...]
>>>> Switching over to lightdm I can get a usable session without -legacy
>>>> as long as I have -input-libinput.  So I'm afraid I have no idea
>>>> what's going on, or even how many problems there are.
>>> As I understand it, lightdm will start X as root unconditionally, so
>>> that will work with or without -legacy.  You want -legacy when using gdm
>>> (or startx) plus have "old drivers".
>>>  * @debian-x: Is the above correct?
>> Yes, any reasonable (read: KMS) setup will work fine without -legacy.
>> In the absence of KMS (e.g. virtualbox, or new hardware not supported by
>> the drivers we ship), you'll need either -legacy or a DM that hasn't
>> been updated to starting X as non-root yet.
>> Cheers,
>> Julien
> Thanks for confirming.
> I also noticed that the wiki has some points on this:
> https://wiki.debian.org/NewInStretch
> """
> Upgrade issues
>   * For many Intel graphics chipsets, the Stretch X server will use the
>     modeset driver instead of the intel driver. The modeset driver may
>     require non-free firmware (firmware-misc-nonfree) to activate
>     features, even on systems which did not use this firmware under
>     Jessie.
>   * For some older graphics chipsets, support has been relegated to
>     "legacy drivers", which require the old setuid X server to run.
>      Install xserver-xorg-legacy if you require one of these drivers.
> """
> I believe the release-notes has the latter point, but not the former.  I
> will add that now.
That doesn't sound correct either.

* xserver-xorg-legacy is now installed by default, so I'm not sure we
need this
* the firmware requirement has nothing to do with the switch from the
"intel" to the "modesetting" (not modeset) driver.


Reply to: