Why does checkproc fail to get session id for a process each time I login? I always find a message like

checkproc: checkproc: can not get session id for process xxxx

in /var/log/messages. Any answer is appreciated.

in /var/log/messages. Any answer is appreciated.

What version of openSUSE is this for? Can you give us the exact error message that you find and if it is in the file more than once? Except for this message, are you having any sort of difficulties with openSUSE? So I do see this error in my openSUSE 11.4 64 bit install, but it happens only every few days and so it does not seem like it is a big deal.

For anyone wanting to look for this on their system, check out my log file viewer script here:

S.L.A.V.E. - SuSE Logfile Automated Viewer Engine - Version 2.55 - Blogs - openSUSE Forums

Thank You,

Thank you, James!

If you receive the same message, it means I shouldn’t have any issues. I use openSUSE 11.4 32 bit install. It just looked weird that it couldn’t get the session id of a specific process.

This S.L.A.V.E. thing seems really useful, I’ll try it.


Happy to help riderplus. If you have any comments on SLAVE, please leave a comment in the blog.

Thank You,

I have been regularly seeing that message with KDE logins. I think I started seeing it when was running 11.3 (which was when I switched from gnome to KDE).

I am treating it as a hardwired message - that is, a message that will always be there and is presumably nothing to worry about. If I try to do a “ps” on the process, it is never there. My wild guess is that it is the Window manager checking up on all processes running in the X session, and there is a short lived process that terminates before it can be checked.

nrickert, I also checked and saw no running process with the associated number. So it must be what you said, although I see no reason why it should prompt the message if it’s short lived. Anyway, nobody’s perfect :slight_smile:

When I first started using linux (around 1995), the way to start X was to run a script. If you wanted the GUI login, then you would name the script “.xsession”.

That script started all of the sessions (GUI windows) that you wanted to run in your session. And it also started a special session called the window manager. Back in those days, I was using “fvwm” as window manager.

If you did not start the window manager, things still worked. It’s just that there would be no menus (for right click on open space, for example), and the windows for your applications would not have any surrounding borders, so would not have any minimize button, maximize button, etc.

As far as I know, X still works the same way. It’s just that we now have the chauffeur driven version, instead of having to drive it ourselves.

When the window manager starts, it has to identify all of the sessions, and then add those borders around them. When an application is using X-windows, it registers that fact with the main X-server (that’s the Xorg process). The window manager looks up what is registered with the X-server, to find where to add borders and do other stuff.

If the window manager finds a registered session, there’s probably no way that it can tell that the session will be short lived.

Thank you for this, nrickert. I didn’t know such details.