http://qa.mandrakesoft.com/show_bug.cgi?id=4828


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From [EMAIL PROTECTED]  2003-09-09 17:45 -------
Verified it works correctly on current cvs of upcoming 9.2. This was problably a
bug in gdm fixed just after 9.2 RC1 was out.


-- 
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: RESOLVED
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 ?

Reply via email to