Re: [Cooker] RC1: KDM after install drops to shell.

[Aleksander Adamowski]

Tarax wrote:

>Hi,
>
>I get exactly the same trouble on my Beta 4.
>Here's my /var/log/messages related lines:
>...
>Sep  4 09:35:41 station kdm[1209]: Unknown session exit code from manager process
>
This message seems to be the only one (in my case) which makes the 
difference in logs between the first X startup (where X is killed 
shortly after loading the window manager) and consequent X startups 
(which are ok). So it seems to be the indication of the problem.

>Hope it will help, please ask for more if needed.
>  
>
I were using IceWM, what Desktop/WindowManager were you using?

Re: [Cooker] RC1: KDM after install drops to shell.

[Aleksander Adamowski]

David Dreggors wrote:

>Yes, I too found this error in the logs along with other errors. Here
>they are:
>...
>  
>
Try to compare the set of log messages when X crashes with the set of 
log messages from subsequent X launches. I'm sure most of those messages 
are irrelevant and are also visible when X and KDM operate normally.

Try to supply only the messages that are characteristic of the problem.

I'm pretty sure that the message about "Unknown session exit code 
from manager process" is only output during the crashing X session.
However, those messages about unrecognized config keys from kdm seem 
harmless - during later X sessions, they are also in the logs, but X 
operates normally.

Re: [Cooker] RC1: KDM after install drops to shell. (startx drop to shell as well)

[Daouda LO]

[EMAIL PROTECTED] writes:

> Hi 
> 
> I do not use KDM at all but I get the same king of trouble when issuing a
> startx command right after initial RC1 boot.
> And of course working OK after another startx.
> 
> If you take a look in an /home/user you get (in my case)
> 
> .bash_logout
> .bash_profile
> .bashrc
> .mailcap
> /tmp
> 
> Right after the first startx command logged with this user account of
> course, X crashes and you get some morefiles
> .xsession-error and .Xauthority and .drakfw + others forders

Could you please give me your .xsession-error ?

> 
> The way I've found to reproduce the problem on my box is to remove the
> .drakfw

Cannot reproduce. Do you install on formated partition (/home ) or do
you have an existing one? 

Run drakfw from a terminal under X (beware to close it with F4 or the close (X) button)

and tell me what happen?

Thanx.

Re: [Cooker] RC1: KDM after install drops to shell. (startx drop to shell as well)

[Daouda LO]

[EMAIL PROTECTED] writes:

> > Could you please give me your .xsession-error ?
> 
> .xsession-error file contains:
> drakfw is /usr/X11R6/bin/drakfw
> 

[...]

> >Run drakfw from a terminal under X (beware to close it with F4 or the close
> (X) button)
> 
> >and tell me what happen?
> 
> Nothing comes up..

Oups, forget to say that drakfw doesn't start when the desktop is
alreday loaded. And this check brings the bug.

Fixed now -> wait for 7mdk.

Thanx for the report.

Re: [Cooker] RC1: KDM after install drops to shell.

[Tarax]

Le Lundi 2 Septembre 2002 20:25, Aleksander Adamowski a écrit :
> Michael E. Jaggers wrote:
> >On Beta 4 and RC1, when installed on a clean HD, when MandrakeLinux 9
> >presents me with the first login screen after the initial installation, I
> >am dropped to a command shell login prompt after selecting a user in KDM.
> >At this point, I have to login as root and launch KDM manually so I can
> >login as a regular user.  Once I do this, I can shutdown the system, and
> >on the next boot, all is OK.
>
> In the logs (var/log/messages), roughly at the moment of that first-time
> KDM shutdown, can you see similar message:
>
>   localhost kdm[958]: Unknown session exit code from manager process
>
> If yes, then I were also seeing this in beta 4 and it hasn't been fixed
> since then.
>
> Details at my webpage:
> >
>
>
> Best Regards,

Hi,

I get exactly the same trouble on my Beta 4.
Here's my /var/log/messages related lines:
...
sep  4 09:34:22 station dm: Starting display manager:
sep  4 09:34:22 station dm: display manager startup succeeded
sep  4 09:34:22 station dm: ^[[65G[^[[1;32m
sep  4 09:34:22 station dm:
sep  4 09:34:22 station rc: Lancement de dm :  succeeded
sep  4 09:34:22 station atd: atd startup succeeded
Sep  4 09:34:23 station saslauthd[1227]: START: saslauthd 1.5.27
Sep  4 09:34:23 station kdm_config[1228]: Unrecognized key 'AllowShutdown' at 
/usr/share/config/kdm/kdmrc:45
Sep  4 09:34:23 station kdm_config[1228]: Unrecognized key 'NoUsers' at 
/usr/share/config/kdm/kdmrc:64
Sep  4 09:34:23 station kdm_config[1228]: Unrecognized key 'Users' at 
/usr/share/config/kdm/kdmrc:71
Sep  4 09:34:23 station kdm_config[1228]: Unrecognized key 'AllowShutdown' at 
/usr/share/config/kdm/kdmrc:81
sep  4 09:34:23 station saslauthd: saslauthd startup succeeded
Sep  4 09:34:23 station saslauthd[1233]: daemon started, listening on /var/lib/sasl/mux
Sep  4 09:34:23 station kdm_config[1228]: Invalid option value 'All' at 
/usr/share/config/kdm/kdmrc:68
...
Sep  4 09:35:41 station kdm[1209]: Unknown session exit code from manager process
Sep  4 09:35:41 station kdm[1209]: Rescanning all config files
...
Sep  4 09:35:41 station kdm_config[2595]: Unrecognized key 'AllowShutdown' at 
/usr/share/config/kdm/kdmrc:45
Sep  4 09:35:41 station kdm_config[2595]: Unrecognized key 'NoUsers' at 
/usr/share/config/kdm/kdmrc:64
Sep  4 09:35:41 station kdm_config[2595]: Unrecognized key 'Users' at 
/usr/share/config/kdm/kdmrc:71
Sep  4 09:35:41 station kdm_config[2595]: Unrecognized key 'AllowShutdown' at 
/usr/share/config/kdm/kdmrc:81

Hope it will help, please ask for more if needed.

Jérémie

Re: [Cooker] RC1: KDM after install drops to shell.

[David Dreggors]

Yes, I too found this error in the logs along with other errors. Here
they are:

Sep  3 03:49:31 tekjunky kernel: Splash status on console 0 changed to
off
Sep  3 03:49:31 tekjunky echo: 0
Sep  3 03:49:31 tekjunky rc: Disabling Boot logo succeeded
Sep  3 03:49:31 tekjunky kdm[1417]: Unknown session exit code from
manager process
Sep  3 03:49:31 tekjunky kdm[1417]: Rescanning all config files
Sep  3 03:49:31 tekjunky kdm_config[2611]: Unrecognized key
'AllowShutdown' at /usr/share/config/kdm/kdmrc:45
Sep  3 03:49:31 tekjunky kdm_config[2611]: Unrecognized key 'NoUsers' at
/usr/share/config/kdm/kdmrc:64
Sep  3 03:49:31 tekjunky kdm_config[2611]: Unrecognized key 'Users' at
/usr/share/config/kdm/kdmrc:71
Sep  3 03:49:31 tekjunky kdm_config[2611]: Unrecognized key
'AllowShutdown' at /usr/share/config/kdm/kdmrc:81
Sep  3 03:49:33 tekjunky gpm[1008]: info:
[/home/flepied/RPM/BUILD/gpm-1.20.0/src/mice.c(1751)]:
Sep  3 03:49:33 tekjunky gpm[1008]: imps2: Auto-detected intellimouse
PS/2
Sep  3 03:50:08 tekjunky login(pam_unix)[2607]: session opened for user
tekjunky by (uid=0)
Sep  3 03:50:08 tekjunky  -- tekjunky[2607]: LOGIN ON vc/1 BY tekjunky
Sep  3 03:51:07 tekjunky dm: display manager startup succeeded
Sep  3 03:51:07 tekjunky kdm_config[2731]: Unrecognized key
'AllowShutdown' at /usr/share/config/kdm/kdmrc:45
Sep  3 03:51:07 tekjunky kdm_config[2731]: Unrecognized key 'NoUsers' at
/usr/share/config/kdm/kdmrc:64
Sep  3 03:51:07 tekjunky kdm_config[2731]: Unrecognized key 'Users' at
/usr/share/config/kdm/kdmrc:71
Sep  3 03:51:07 tekjunky kdm_config[2731]: Unrecognized key
'AllowShutdown' at /usr/share/config/kdm/kdmrc:81
Sep  3 03:51:07 tekjunky kdm_config[2731]: Invalid option value 'All' at
/usr/share/config/kdm/kdmrc:68
Sep  3 03:51:17 tekjunky gpm[1008]: info:
[/home/flepied/RPM/BUILD/gpm-1.20.0/src/mice.c(1751)]:
Sep  3 03:51:17 tekjunky gpm[1008]: imps2: Auto-detected intellimouse
PS/2
Sep  3 03:51:34 tekjunky login(pam_unix)[2607]: session closed for user
tekjunky
Sep  3 03:51:42 tekjunky kde3(pam_unix)[2733]: session opened for user
tekjunky by (uid=0)


These messages are EXACTLY during the time from the first graphical
login screenthe crash that leaves you at tty1 or VC/1 as mentioned
above and me logging in via tty1.

Hope this helps.

David

On Mon, 2002-09-02 at 14:25, Aleksander Adamowski wrote:
> Michael E. Jaggers wrote:
> 
> >On Beta 4 and RC1, when installed on a clean HD, when MandrakeLinux 9
> >presents me with the first login screen after the initial installation, I
> >am dropped to a command shell login prompt after selecting a user in KDM. 
> >At this point, I have to login as root and launch KDM manually so I can
> >login as a regular user.  Once I do this, I can shutdown the system, and
> >on the next boot, all is OK.
> >
> >  
> >
> In the logs (var/log/messages), roughly at the moment of that first-time KDM 
>shutdown, can you see similar message:
> 

Re: [Cooker] RC1: KDM after install drops to shell.

[Michael E. Jaggers]

In <[EMAIL PROTECTED]>, on 09/02/02 
   at 08:25 PM, Aleksander Adamowski <[EMAIL PROTECTED]> said:

>Michael E. Jaggers wrote:

>>On Beta 4 and RC1, when installed on a clean HD, when MandrakeLinux 9
>>presents me with the first login screen after the initial installation, I
>>am dropped to a command shell login prompt after selecting a user in KDM. 
>>At this point, I have to login as root and launch KDM manually so I can
>>login as a regular user.  Once I do this, I can shutdown the system, and
>>on the next boot, all is OK.
>>
>>  
>>
>In the logs (var/log/messages), roughly at the moment of that first-time
>KDM shutdown, can you see similar message:

>  localhost kdm[958]: Unknown session exit code from manager process

>If yes, then I were also seeing this in beta 4 and it hasn't been fixed 
>since then.

>Details at my webpage:
>


>Best Regards,

A similar message is in /var/log/messages.  It says:

  kdm(1128): Unknown session exit code from manager process

-- 
---
"Michael E. Jaggers" <[EMAIL PROTECTED]>
---

Re: [Cooker] RC1: KDM after install drops to shell.

[David Dreggors]

Actually, I am in Beta 4 and it is ALL the time for me. Not just first
boot! every time I log in I have to start dm over!

On Mon, 2002-09-02 at 14:52, Frederic Lepied wrote:
> Buchan Milne <[EMAIL PROTECTED]> writes:
> 
> > Michael E. Jaggers wrote:
> > | On Beta 4 and RC1, when installed on a clean HD, when MandrakeLinux 9
> > | presents me with the first login screen after the initial installation, I
> > | am dropped to a command shell login prompt after selecting a user in KDM.
> > | At this point, I have to login as root and launch KDM manually so I can
> > | login as a regular user.  Once I do this, I can shutdown the system, and
> > | on the next boot, all is OK.
> > |
> > 
> > Are you sure it's ok? I suspect the VT X is running on is being killed
> > when init finishes, and starts up the new VTs.
> > 
> > Instead of logging in immediately, wait 30 seconds or so, and it will
> > happen.
> > 
> > Anyway, you can also just restart the dm service, instead of launching kdm:
> > 
> > # service dm start
> > 
> > Is this going to be fixed??
> 
> I'm tracking it but it's very hard to debug because it only happens on
> the first boot...
> -- 
> Fred - May the source be with you
> 

Re: [Cooker] RC1: KDM after install drops to shell.

[Frederic Lepied]

Buchan Milne <[EMAIL PROTECTED]> writes:

> Michael E. Jaggers wrote:
> | On Beta 4 and RC1, when installed on a clean HD, when MandrakeLinux 9
> | presents me with the first login screen after the initial installation, I
> | am dropped to a command shell login prompt after selecting a user in KDM.
> | At this point, I have to login as root and launch KDM manually so I can
> | login as a regular user.  Once I do this, I can shutdown the system, and
> | on the next boot, all is OK.
> |
> 
> Are you sure it's ok? I suspect the VT X is running on is being killed
> when init finishes, and starts up the new VTs.
> 
> Instead of logging in immediately, wait 30 seconds or so, and it will
> happen.
> 
> Anyway, you can also just restart the dm service, instead of launching kdm:
> 
> # service dm start
> 
> Is this going to be fixed??

I'm tracking it but it's very hard to debug because it only happens on
the first boot...
-- 
Fred - May the source be with you

Re: [Cooker] RC1: KDM after install drops to shell.

[Aleksander Adamowski]

Michael E. Jaggers wrote:

>On Beta 4 and RC1, when installed on a clean HD, when MandrakeLinux 9
>presents me with the first login screen after the initial installation, I
>am dropped to a command shell login prompt after selecting a user in KDM. 
>At this point, I have to login as root and launch KDM manually so I can
>login as a regular user.  Once I do this, I can shutdown the system, and
>on the next boot, all is OK.
>
>  
>
In the logs (var/log/messages), roughly at the moment of that first-time KDM shutdown, 
can you see similar message:

  localhost kdm[958]: Unknown session exit code from manager process

If yes, then I were also seeing this in beta 4 and it hasn't been fixed 
since then.

Details at my webpage:



Best Regards,

-- 
Olo
GG#: 274614
ICQ UIN: 19780575 
http://olo.office.altkom.com.pl

Re: [Cooker] RC1: KDM after install drops to shell.

[Buchan Milne]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Michael E. Jaggers wrote:
| On Beta 4 and RC1, when installed on a clean HD, when MandrakeLinux 9
| presents me with the first login screen after the initial installation, I
| am dropped to a command shell login prompt after selecting a user in KDM.
| At this point, I have to login as root and launch KDM manually so I can
| login as a regular user.  Once I do this, I can shutdown the system, and
| on the next boot, all is OK.
|

Are you sure it's ok? I suspect the VT X is running on is being killed
when init finishes, and starts up the new VTs.

Instead of logging in immediately, wait 30 seconds or so, and it will
happen.

Anyway, you can also just restart the dm service, instead of launching kdm:

# service dm start

Is this going to be fixed??

- --
|Registered Linux User #182071-|
Buchan MilneMechanical Engineer, Network Manager
Cellphone * Work+27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE9c5ZgrJK6UGDSBKcRApeTAJ0ZyiHXxxbLXcKYhmoB5/tBBmaMsQCeMVRZ
S0TG4fjrFOe+4HcmnNNhP4A=
=tBqh
-END PGP SIGNATURE-