Hi
This morning my users came in to find that they had had their locked F16 kde sessions logged out. Indications are that this happened about the time of our nightly yum update. The systems had not rebooted so we can probably rule out a power glitch.
I'd like to try to find out what caused this since we'd rather it didn't happen regularly.
There were quite a few updates that came in early this morning, but as a starting point I was wondering if the logout was a possible side effect of the kde updates? It looks like kdebase-workspace*, kdm, ksysguard*, libkworkspace, phonon* and plasma-scriptengine-python were updated?
Has anyone else noticed such an unscheduled logout?
Thanks
Roderick Johnstone
Roderick Johnstone wrote:
This morning my users came in to find that they had had their locked F16 kde sessions logged out. Indications are that this happened about the time of our nightly yum update. The systems had not rebooted so we can probably rule out a power glitch.
I'd look in these users' ~/.xsession-errors for anything suspicious. Them losing their X session likely indicates an X server crash of some sort.
-- rex
On 10/01/12 13:44, Rex Dieter wrote:
Roderick Johnstone wrote:
This morning my users came in to find that they had had their locked F16 kde sessions logged out. Indications are that this happened about the time of our nightly yum update. The systems had not rebooted so we can probably rule out a power glitch.
I'd look in these users' ~/.xsession-errors for anything suspicious. Them losing their X session likely indicates an X server crash of some sort.
Many people have logged in again, and I think that has created new .xsession-errors files, but I did find one .xsession-errors file with relevant info that I'm appending. This one was an nx session, in case you were wondering about the high port number.
Does that log suggest what happened to you? Something sent a SIGTERM? What would do that?
Roderick
nepomukcontroller: Fatal IO error: client killed kactivitymanagerd: Fatal IO error: client killed plasma-desktop: Fatal IO error: client killed kwin: Fatal IO error: client killed kglobalaccel: Fatal IO error: client killed kded4: Fatal IO error: client killed ksmserver: Fatal IO error: client killed klauncher: Exiting on signal 15 XIO: fatal IO error 4 (Interrupted system call) on X server ":1046" after 23 requests (23 known processed) with 0 events remaining. konsole: Fatal IO error: client killed
Received signal:15->'Terminated'kblankscrn.kss: Fatal IO error: client killed kscreenlocker: Fatal IO error: client killed
Received signal:15->'Terminated'
OK
ProcessControl: Application '/usr/bin/nepomukservicestub' stopped unexpected (Process crashed) Application '/usr/bin/nepomukservicestub nepomukstorage' crashed. No restart! g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
Received signal:15
On 01/10/2012 08:19 AM, Roderick Johnstone wrote:
On 10/01/12 13:44, Rex Dieter wrote:
Roderick Johnstone wrote:
This morning my users came in to find that they had had their locked F16 kde sessions logged out. Indications are that this happened about the time of our nightly yum update. The systems had not rebooted so we can probably rule out a power glitch.
I'd look in these users' ~/.xsession-errors for anything suspicious. Them losing their X session likely indicates an X server crash of some sort.
Many people have logged in again, and I think that has created new .xsession-errors files, but I did find one .xsession-errors file with relevant info that I'm appending. This one was an nx session, in case you were wondering about the high port number.
Does that log suggest what happened to you? Something sent a SIGTERM? What would do that?
XIO: fatal IO error 4 (Interrupted system call) on X server ":1046" after 23 requests (23 known processed) with 0 events remaining. konsole: Fatal IO error: client killed
This one is a strong hint that the X server went away alright.
-- rex
-
Rex Dieter -
Roderick Johnstone