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

Wed Apr 18 14:46:28 CEST 2012

On 18/04/12 13:09, Colin Guthrie wrote:
+> 'Twas brillig, and Colin Guthrie at 18/04/12 12:57 did gyre and
+> gimble:
+>> 'Twas brillig, and Anne Wilson at 18/04/12 12:32 did gyre and
+>> gimble:
+>>> On 17/04/12 21:22, Colin Guthrie wrote:
+>>>> 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.
+>> 
+>> Yeah it seems to be related to the tablet... can you try just
+>> moving the xorg.conf out the way (mv /etc/X11/xorg.conf
+>> /etc/X11/xorg.conf.ignore) and reboot and see if it's happier?
+> 
+> Actually I don't think it's that in retrospect... There seems to be
+> two seconds where X just sits and waits. Then it closes down
+> normally.
+> 
+> [    70.650] (**) Option "xkb_options" "compose:rwin" [    72.501]
+> (II) evdev: Power Button: Close
+> 
+> So the next step is to see where the rest of the errors come from.
+> 
+> 1. What display manager are you using? I'm guessing KDM. If so what
+> does /var/log/kdm.log say?
+> 
+> I suspect it has those dbus related errors... but it would be nice
+> to confirm.
+> 
+> I'm pretty sure it's KDM that failing and subsequently bringing X
+> down with it. I'll see if I can reproduce with KDM here.
+> 
+kdm.log was >5000 lines and full of identical lines, so I mv'd it.  The
+attached is a clean kdm.log.  Those 29 lines have the answer :-)
+
+Anne
+-- 
+Need KDE help? Try
+http://userbase.kde.org or
+http://forum.kde.org
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: kdm.log
+Type: text/x-log
+Size: 1719 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120418/3836a063/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/3836a063/attachment-0001.asc>
+