On 04.10.2013 14:39, Alan McKinnon wrote:
> On 04/10/2013 14:39, Andreas Prieß wrote:
>> On 04.10.2013 13:20, Andreas Prieß wrote:
>>> Since I don't know the cause and didn't find a way to debug this, here
>>> are the symptoms:
>>>
>>> Ever since media-libs/mesa >= 9.1 went stable I had the problem, that
>>> the switch from Xfce on VT7 back to VT1 on shutdown fails. The screen
>>> goes black and does not show anything, but the system halts as normal.
>>> It is not possible to switch to VT1 by keyboard while the shutdown is
>>> still in progress when this has happened.
>>>
>>> I can't find anything in the Xorg or other log files according to this
>>> problem. Can't find anything related in Gentoo bugzilla or searching the
>>> web...
>>>
>>> The problem always disappeared by downgrading to mesa < 9.1, but that
>>> now requires other packages to be downgraded too, so I'd like to resolve
>>> this.
>>>
>>> It is an AMD64 system with an ATI Barts PRO [Radeon HD 6850] using KMS,
>>> desktop session with Xfce started by x11-misc/lightdm.
>>>
>>> Any hints on how to debug this problem would be highly appreciated.
>>
>> Maybe this is relevant...
>>
>> Xorg is running a dual head layout using xinerama instead of randr.
>> Composite disabled since it does not work with this config.
>>
>>
> 
> Your kernel config in the other reply looks fine to me.
> 
> This dual head setup - do you have one large desktop across two
> monitors, or two screens configured in xorg.conf? I can never quite
> remember what xinerama does (I think it's the first one)
> 
> Can you reproduce the problem using just one configured monitor?

The dual head setup with xinerama has two screens configured. The
monitors have different resolutions and windows, desktop panels and
things got placed in invisible areas otherwise (with Xfce at least).

So, there is a new fact: I can NOT reproduce it with only one screen.

If I start X without my config files and let it configure one screen
automatically, the switch to VT1 on shutdown works as expected.

Any hints for the next step? File a bug with mesa? Try other things?


-- 
Andreas

Reply via email to