http://qa.mandrakesoft.com/show_bug.cgi?id=4828
------- Additional Comments From [EMAIL PROTECTED] 2003-22-08 00:07 ------- ok I came back from where I was. startkde and then mcc to disable autologin to a user. That's a bad idea anyway from a security point of view... Thanks for help. It was really a pain to come back to X with no window move possible : you get to grasp the meaning of "window manager". I'll wait till it's corrected and may give it a second chance. In MCC an enhancement may be to warn that the appearance of login will change (that may be evident... but I only realized it at reboot). -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: drakxtools-9.2-0.31mdk in fact... (hard to follow Mandrake 9.2 beta 2) I get an ugly window borderless at boot of Gnome (just before splash screen) saying : C'est une session de secours Gnome. Vous serez connect� dans la session "Default" de GNOME sans aucun script de d�marrage au lancement. C'est seulement pour corriger Les probl�mes de votre installation No indication of the bug causing this sudden apparition... Afterwards, I'm logged normally (all in english neverthelesss... accented characters appearing as a square in vi...). In /var/log/messages the only relevant error is : Aug 20 20:52:25 BenAthlux gconfd (baud-2696): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0 Aug 20 20:52:25 BenAthlux gconfd (baud-2696): Resolved address "xml:readwrite:/home/baud/.gconf" to a writable config source at position 1 Aug 20 20:52:25 BenAthlux gconfd (baud-2696): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2 (other appear, believe me, but this very one is new and only appears today) What I did before : - updates with cooker - solve lilo problems with dual booting in Linux MdK9.1.... (I'm going to file a bug as well...) - and finally configure autoboot to a user What should I do now ?
