diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-April/014381.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-April/014381.html | 164 |
1 files changed, 164 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-April/014381.html b/zarb-ml/mageia-dev/2012-April/014381.html new file mode 100644 index 000000000..7e1bbff96 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-April/014381.html @@ -0,0 +1,164 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Broken database problem solved but not all well + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Broken%20database%20problem%20solved%20but%20not%20all%20well&In-Reply-To=%3C4F8DD11A.6010400%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="014371.html"> + <LINK REL="Next" HREF="014411.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Broken database problem solved but not all well</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Broken%20database%20problem%20solved%20but%20not%20all%20well&In-Reply-To=%3C4F8DD11A.6010400%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] Broken database problem solved but not all well">mageia at colin.guthr.ie + </A><BR> + <I>Tue Apr 17 22:22:50 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="014371.html">[Mageia-dev] Broken database problem solved but not all well +</A></li> + <LI>Next message: <A HREF="014411.html">[Mageia-dev] Broken database problem solved but not all well +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#14381">[ date ]</a> + <a href="thread.html#14381">[ thread ]</a> + <a href="subject.html#14381">[ subject ]</a> + <a href="author.html#14381">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Colin Guthrie at 17/04/12 16:49 did gyre and gimble: +><i> 'Twas brillig, and Anne Wilson at 17/04/12 15:13 did gyre and gimble: +</I>>><i> On 17/04/12 10:00, Colin Guthrie wrote: +</I>>>><i> All of this should be fixed when we update all the legacy +</I>>>><i> initscripts. +</I>>><i> +</I>>>><i> In the mean time if you go into /etc/init.d/ and do: +</I>>><i> +</I>>>><i> grep -c "INIT INFO" *| grep -vE +</I>>>><i> "(halt|killall|mandrake_.*|reboot|single|functions):" | grep :0$ +</I>>><i> +</I>>><i> +</I>>>><i> This should show you what initscripts you have on your system that +</I>>>><i> do not have LSB header information. +</I>>><i> +</I>>>><i> If you let me know the results of that command I'll look +</I>>>><i> specifically at this one so I can push a fix for you sooner rather +</I>>>><i> than latter (tho' all will get fixed before RC). +</I>>><i> +</I>>><i> I've been over and over that command, and I'm certain I've typed it +</I>>><i> right, but sending it to a text file always produced a 0byte file, so +</I>>><i> I tried it without the redirect, and there was a hesitation - working +</I>>><i> time - then the prompt returned - no output at all. Any idea what +</I>>><i> could be wrong? +</I>><i> +</I>><i> Well perhaps there is something more going on regarding loops. I'll see +</I>><i> if I can find something out here... I think others have reported this +</I>><i> too so it might not be the only cause of the loops. I'll find it +</I>><i> eventually tho'!! +</I> +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), 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: +<A HREF="https://bugs.mageia.org/show_bug.cgi?id=5426">https://bugs.mageia.org/show_bug.cgi?id=5426</A> + + +-- + +Colin Guthrie +colin(at)mageia.org +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A> +Open Source: + Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A> + PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A> + Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="014371.html">[Mageia-dev] Broken database problem solved but not all well +</A></li> + <LI>Next message: <A HREF="014411.html">[Mageia-dev] Broken database problem solved but not all well +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#14381">[ date ]</a> + <a href="thread.html#14381">[ thread ]</a> + <a href="subject.html#14381">[ subject ]</a> + <a href="author.html#14381">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |