On 12/07/2011 02:02 PM, Adam Jackson wrote:
> On 12/7/11 12:20 PM, Clyde E. Kunkel wrote:
>> On 12/06/2011 12:35 PM, Adam Jackson wrote:
>>> On 12/6/11 11:27 AM, Clyde E. Kunkel wrote:
>>>
[ 428.783] Server terminated successfully (0). Closing log file.
>>>
>>> This message is there for a reas
On 12/7/11 12:20 PM, Clyde E. Kunkel wrote:
> On 12/06/2011 12:35 PM, Adam Jackson wrote:
>> On 12/6/11 11:27 AM, Clyde E. Kunkel wrote:
>>
>>> [ 428.783] Server terminated successfully (0). Closing log file.
>>
>> This message is there for a reason. It means the X server is terminating
>> "normall
On 12/06/2011 12:35 PM, Adam Jackson wrote:
> On 12/6/11 11:27 AM, Clyde E. Kunkel wrote:
>
>> [ 428.783] Server terminated successfully (0). Closing log file.
>
> This message is there for a reason. It means the X server is terminating
> "normally", ie, because the session has gone away.
>
> Check
On 12/6/11 11:27 AM, Clyde E. Kunkel wrote:
> [ 428.783] Server terminated successfully (0). Closing log file.
This message is there for a reason. It means the X server is
terminating "normally", ie, because the session has gone away.
Check in ~/.xsession-errors for relevant messages, or in
On Tue, 2011-12-06 at 11:27 -0500, Clyde E. Kunkel wrote:
> In current rawhide on one of my test systems (actual hardware, not
> virtual machine) when I unplug/replug the usb mouse/keyboard (they are
> on a kvm switch) the xserver restarts. This started about a month ago
> right after the rebui
In current rawhide on one of my test systems (actual hardware, not
virtual machine) when I unplug/replug the usb mouse/keyboard (they are
on a kvm switch) the xserver restarts. This started about a month ago
right after the rebuild of the X stack packages (not saying that is the
culprit, just
