[Mageia-dev] Broken database problem solved but not all well

Wed Apr 18 13:32:46 CEST 2012

On 17/04/12 21:22, Colin Guthrie wrote:
+> 'Twas brillig, and Colin Guthrie at 17/04/12 16:49 did gyre and
+> gimble:
+>> 'Twas brillig, and Anne Wilson at 17/04/12 15:13 did gyre and
+>> gimble:
+>>> On 17/04/12 10:00, Colin Guthrie wrote:
+>>>> All of this should be fixed when we update all the legacy 
+>>>> initscripts.
+>>> 
+>>>> In the mean time if you go into /etc/init.d/ and do:
+>>> 
+>>>> grep -c "INIT INFO" *| grep -vE 
+>>>> "(halt|killall|mandrake_.*|reboot|single|functions):" | grep
+>>>> :0$
+>>> 
+>>> 
+>>>> This should show you what initscripts you have on your system
+>>>> that do not have LSB header information.
+>>> 
+>>>> If you let me know the results of that command I'll look 
+>>>> specifically at this one so I can push a fix for you sooner
+>>>> rather than latter (tho' all will get fixed before RC).
+>>> 
+>>> I've been over and over that command, and I'm certain I've typed
+>>> it right, but sending it to a text file always produced a 0byte
+>>> file, so I tried it without the redirect, and there was a
+>>> hesitation - working time - then the prompt returned - no output
+>>> at all.  Any idea what could be wrong?
+>> 
+>> Well perhaps there is something more going on regarding loops. I'll
+>> see if I can find something out here... I think others have
+>> reported this too so it might not be the only cause of the loops.
+>> I'll find it eventually tho'!!
+> 
+> OK, so that syslog related ordering cycle was down to a patch that
+> was supposed to prevent such a cycle but actually seemed to create it
+> it.
+> 
+> Confirmed the cycle on two machines here and confirmed dropping the 
+> patch fixes it.
+> 
+> Hey ho.
+> 
+> 
+> I no longer thing that this would be a big problem overall however.
+> 
+> 
+> As you do not have any legacy initscripts messing things up, I think
+> the problem you now face is more simple. We need to find out exactly
+> what's wrong.
+> 
+> 
+> I guess the next stage is to: 1. Boot. 2. Assuming X does not start,
+> switch to tty2 3. Get the output of: systemctl show prefdm.service 4.
+> Assuming it's actually tried to start it (look for dates in the 
+> ActiveEnterTimestamp variable near the top),
+
+ActiveEnterTimestamp=Tues, 17 Apr 2012 14:47:50 +0100 (yes, it was on
+all night :-) )
+
+then look in
+> /var/log/Xorg.0.log.
+> 
+
+> If you happen to have a radeon, and it's using the vesa driver it
+> could be the same problem Oliver is seeing: 
+> https://bugs.mageia.org/show_bug.cgi?id=5426
+> 
+It's Intel.  It seems to be a bit unhappy that the Wacom tablet isn't
+attached, but ISTR that the same thing happened when it was attached so
+I doubt if that is relevant.  The logfile is attached.
+
+Anne
+-- 
+Need KDE help? Try
+http://userbase.kde.org or
+http://forum.kde.org
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: Xorg.0.log
+Type: text/x-log
+Size: 36747 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120418/4622fd07/attachment-0001.log>
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 262 bytes
+Desc: OpenPGP digital signature
+URL: </pipermail/mageia-dev/attachments/20120418/4622fd07/attachment-0001.asc>
+