[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

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.

- -- 
Need KDE help? Try
http://userbase.kde.org or
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


More information about the Mageia-dev mailing list