When a missing X11 driver is detected, the harddrake service at boot-up tries to install the missing package using urpmi. However, it does so before the network is brought up, making urpmi fail if all urpmi sources are network installations, leaving the user with broken X In practice I encountered this problem when changing my cauldron KVM virtual machine to use spice and qxl graphics in virt-manager. I did not have the qxl driver installed in my mageia VM and so haddrake tried to install it when booting the system, but failed because there was no network connection. Easy solution is to try to bring up the network first before calling urpmi. That would still fail if harddrake needs to install packages to make the network functional, but at least the example of missing X drivers would be fixed.
Source RPM: harddrake => drakxtools
Thierry, so urpmi need just to check the network ?
Assignee: bugsquad => thierry.vignaudSource RPM: drakxtools => urpmi
or harddrake should fallback on vesa/fb/whatever
Source RPM: urpmi => urpmi harddrake-ui
Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED. @ Thierry Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
3-monthly ping
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
no replies to pings, nobody else reported this issue, so closing as OLD Please reopen if needed and tell with wich version(s) it is still valid
Status: NEW => RESOLVEDResolution: (none) => OLD