From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-September/018990.html | 123 ++++++++++++++++++++++++++ 1 file changed, 123 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-September/018990.html (limited to 'zarb-ml/mageia-dev/2012-September/018990.html') diff --git a/zarb-ml/mageia-dev/2012-September/018990.html b/zarb-ml/mageia-dev/2012-September/018990.html new file mode 100644 index 000000000..f0f2b755f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-September/018990.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] Fwd: Re: M3 won't complete boot after update + + + + + + + + + +

[Mageia-dev] Fwd: Re: M3 won't complete boot after update

+ Anne Wilson + annew at kde.org +
+ Thu Sep 27 16:06:01 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 27/09/12 14:37, Colin Guthrie wrote:
+> Ahh a nice simple answer in the end!
+> 
+> I probably should have been more persistant in asking this question
+>  initially (I think I did mention it in an earlier mail, but also 
+> asked a whole bunch of other stuff in a "get all the debug
+> possible all at once" fit of pseudo efficiency! Kinda backfired a
+> bit!
+> 
+I don't recall seeing that question, so yes, it probably got hidden
+among the rest :-)
+> 
+>>> So - I now have M3 working - with the display problem that I 
+>>> already knew about, but that's definitely KDE related, as a 
+>>> second user doesn't see it, so now I can work on that.
+>>> 
+>>> The only remaining question is "how did a working system end up
+>>>  without a display driver?"
+> Well, it's perhaps this scenario:
+> 
+> x11-driver-video was installed initially and it pulled in lots of 
+> individual display drivers, including intel.
+> 
+> Due to an xorg update, one of the drivers that is required by 
+> x11-driver-video had to be removed (due to no longer being 
+> supported) which resulted in x11-driver-video also being removed, 
+> thus orphaning all the drivers it initially pulled in, including
+> the intel one.
+> 
+> It's quite easy to happen really, this is one of the many reasons I
+>  never, use the --auto-orphans feature. I use urpmq --not-available
+> to do my tidy ups.
+> 
+Actually, being naturally rather cautious, I usually just ignore the
+invitation to use auto-orphans, in the belief that the additional
+packages will do no harm.  I certainly won't be using it again :-)
+
+In view of this problem, though, I wonder whether it is such a good
+idea to end updates with that invitation.
+
+Anne
+- -- 
+Need KDE help? Try
+http://userbase.kde.org or
+http://forum.kde.org
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlBkXUIACgkQj93fyh4cnBfrfACfTwQPg3IlILOq0LBPUWlPVt9C
+CdUAnifnp/+6V7J4VsbtnaGBJyPGzki0
+=Lg5I
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1