summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20110922/005438.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-discuss/20110922/005438.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-discuss/20110922/005438.html')
-rw-r--r--zarb-ml/mageia-discuss/20110922/005438.html208
1 files changed, 208 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20110922/005438.html b/zarb-ml/mageia-discuss/20110922/005438.html
new file mode 100644
index 000000000..156830de8
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20110922/005438.html
@@ -0,0 +1,208 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-discuss] troubles with update ended with totally dead system.
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20troubles%20with%20update%20ended%20with%20totally%0A%09dead%09system.&In-Reply-To=%3Cj5e3r4%24ggc%241%40dough.gmane.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="005441.html">
+ <LINK REL="Next" HREF="005439.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] troubles with update ended with totally dead system.</H1>
+ <B>Juan R. de Silva</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20troubles%20with%20update%20ended%20with%20totally%0A%09dead%09system.&In-Reply-To=%3Cj5e3r4%24ggc%241%40dough.gmane.org%3E"
+ TITLE="[Mageia-discuss] troubles with update ended with totally dead system.">juan.r.d.silva at gmail.com
+ </A><BR>
+ <I>Thu Sep 22 03:43:00 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005441.html">[Mageia-discuss] Testers needed for siproxd.
+</A></li>
+ <LI>Next message: <A HREF="005439.html">[Mageia-discuss] [SOLVED] Re: troubles with update ended with totally dead system.
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5438">[ date ]</a>
+ <a href="thread.html#5438">[ thread ]</a>
+ <a href="subject.html#5438">[ subject ]</a>
+ <a href="author.html#5438">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Wed, 21 Sep 2011 20:05:50 +0200, Maarten Vanraes wrote:
+
+&gt;<i> Op woensdag 21 september 2011 11:32:24 schreef Claire Robinson:
+</I>&gt;&gt;<i> On 21/09/11 02:52, Juan R. de Silva wrote:
+</I>&gt;&gt;<i> &gt; Hey folks,
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; I do not know if it could be seen as a kind of a contribution...
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; I installed Mageia 1 almost as soon as it was released for evaluation
+</I>&gt;&gt;<i> &gt; purposes on Dell Latitude d820. Mine is a multiboot environment with
+</I>&gt;&gt;<i> &gt; several distros like Ubuntu Lucid, Fedora 15, Arch, SL 6.1, and a
+</I>&gt;&gt;<i> &gt; couple of others installed.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; I kept playing with it from time to time (my main systems for now are
+</I>&gt;&gt;<i> &gt; Ubuntu Lucid on laptop, and Debian Squeeze on my workstation). I
+</I>&gt;&gt;<i> &gt; should say I was quite impressed, especially considering short time
+</I>&gt;&gt;<i> &gt; Mageia exists.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; Then troubles started. On one of next system updates I had these:
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; Sorry, the following packages cannot be selected:
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; - kdebase4-runtime-4.6.5-1.1.mga1.i586 (due to conflicts with
+</I>&gt;&gt;<i> &gt; soprano- plugin-virtuoso-2.6.0-0.1.mga1.i586)
+</I>&gt;&gt;<i> &gt; - kipi-plugins-expoblending-1.9.0-3.1.mga1.i586 -
+</I>&gt;&gt;<i> &gt; task-kde4-4.6.5-0.mga1.noarch
+</I>&gt;&gt;<i> &gt; - task-kde4-minimal-4.6.5-0.mga1.noarch (due to conflicts with
+</I>&gt;&gt;<i> &gt; soprano- plugin-virtuoso-2.6.0-0.1.mga1.i586)
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; google provided with one link only. It was Mageia forum, not exactly
+</I>&gt;&gt;<i> &gt; my case but had enough to be considered helpful.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; 'rpm -e --nodeps soprano-plugin-virtuoso' revealled the plugin was
+</I>&gt;&gt;<i> &gt; not installed at all. A little weird, update conflicting with a not
+</I>&gt;&gt;<i> &gt; installed packages, &quot;never mind&quot; I said.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; After run 'urpmi soprano-plugin-virtuoso' and installing the plugin I
+</I>&gt;&gt;<i> &gt; happily get get rid of almost all the above warnings. But still had
+</I>&gt;&gt;<i> &gt; this one:
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; Sorry, the following package cannot be selected:
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; - kipi-plugins-expoblending-1.9.0-3.1.mga1.i586
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; Well, that was quite a progress.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; I run 'urpmi kipi-plugins-expoblending' and on the next update
+</I>&gt;&gt;<i> &gt; attempt I did not get any restricting warnings/errors. So far so
+</I>&gt;&gt;<i> &gt; good. Finally I could proceed with the update.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; It seemed to complete well: no warnings, no errors. Except one little
+</I>&gt;&gt;<i> &gt; dirty thing - the system failed to boot after restart. It stuck at
+</I>&gt;&gt;<i> &gt; GRUB prompt with no errors displayed, just a word &quot;GRUB&quot;. No reaction
+</I>&gt;&gt;<i> &gt; on any key, not 'e', not 'c', not 'shift' button, not any others. Not
+</I>&gt;&gt;<i> &gt; even Ctl- Alt-Del. The only way to get out of there was pressing
+</I>&gt;&gt;<i> &gt; Power Off button.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; Booting from SystemRescueCD and reinstalling grub helped nothing.
+</I>&gt;&gt;<i> &gt; Plain dead system.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; But this was a climax. I get to the Mageia forum, trying to search
+</I>&gt;&gt;<i> &gt; for a clue and get this:
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; &quot;Sorry but you cannot use search at this time. Please try again in a
+</I>&gt;&gt;<i> &gt; few minutes.&quot;
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; And no, folks, I've not reported any bugs. Sorry, far to many... :-(
+</I>&gt;&gt;<i> &gt; At the end I did not try to anything funny here. Just a regular
+</I>&gt;&gt;<i> &gt; system update.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> This is a known bug, it *should* be solved now.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> There is a bug report at <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2097">https://bugs.mageia.org/show_bug.cgi?id=2097</A>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> It was quite a bad bug as it did break the update but it brought to
+</I>&gt;&gt;<i> light the now infamous bug 2317 -
+</I>&gt;&gt;<i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2317">https://bugs.mageia.org/show_bug.cgi?id=2317</A> - which all updates have
+</I>&gt;&gt;<i> to be checked against.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> We have begun linking any required packages into updates media to
+</I>&gt;&gt;<i> prevent any recurrence of that unfortunate incident. If any do slip
+</I>&gt;&gt;<i> through the net then the affect you will see is that MageiaUpdate will
+</I>&gt;&gt;<i> give an error saying a certain package cannot be selected. Please do
+</I>&gt;&gt;<i> report this if you experience it!
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> This only affects MageiaUpdate, so you can still perform the update
+</I>&gt;&gt;<i> from the command line as root (urpmi --auto-update) or by installing
+</I>&gt;&gt;<i> the updated packages in rpmdrake instead.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Hopefully we are on top of this now though and a permanent solution is
+</I>&gt;&gt;<i> being worked on behind the scenes.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Sorry if you had a bad experience with this.
+</I>&gt;<i>
+</I>&gt;<i> Also <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2070">https://bugs.mageia.org/show_bug.cgi?id=2070</A>
+</I>&gt;<i>
+</I>&gt;<i> again, if there is bugs, try to confirm or give help.
+</I>
+Well, with the picture in hand I'd find it quite difficult to report any
+particular bug.
+
+The whole thing involves to many steps to go through and to identify what
+the problem actually was, and when, and what has happened.
+
+I still have an image of the partition with Mageia which was maid at the
+point initial update problem manifested itself reporting a number of
+files that cannot be selected. It would take me just several minutes to
+restore it. I would not mind to do it to help.
+
+However, I would do it only if I know exactly what and at which point
+would be in interest to report and provide being helpful to developers.
+If you or somebody else would be interested to guide me I could do it.
+
+There are only 3 obstacles here. First I'm a GNOME user, so I know little
+about KDE. Second, I've never used neither Mandriva nor certainly Mageia
+before and know about them even less. And third, I'm going to be quite
+busy next month, so there might be some delays in my participation.
+
+If all the above is OK, then I could commit to do it.
+
+&gt;<i> btw: with the grub issue it would be interesting if you could report it
+</I>&gt;<i> and post the /root/drakx/install.log file in it. perhaps something odd
+</I>&gt;<i> happened during the install.
+</I>
+I could report the file content but I'm afraid it would be of a little
+value, since its timestamp is 2011.08.09 when the crash happened on
+2011.09.20. So, the file contains only an outdated information.
+
+&gt;<i> btw: was it installed using DVD or liveCD?
+</I>
+Sincerely I do not recall. I did not pay attention to details at that
+point, since all I wanted was to give Mageia a try. However I more
+inclined to think it was a liveCD.
+
+The installation was simple. I just accepted all defaults, except the
+location of / and location of GRUB installation. I installed Mageia on a
+separate partition and installed GRUB on the same partition. My Ubuntu
+Lucid was chainloding it. Typical multiboot install. It worked fine up to
+the system update as I described.
+
+Personally, I suspect Mageia had trouble with the GRUB being installed
+not to MBR but in its own partition. But this is a pure speculation.
+
+Another thing to mention. The first time I get the first complains while
+trying to update the system was quite a long time ago, about over a
+month. Since Mageia for was just a &quot;test drive&quot;, I left it as it was. So,
+yesterday's update was quite a massive one. If I remember correctly
+something close to 350-400MB.
+
+
+</PRE>
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005441.html">[Mageia-discuss] Testers needed for siproxd.
+</A></li>
+ <LI>Next message: <A HREF="005439.html">[Mageia-discuss] [SOLVED] Re: troubles with update ended with totally dead system.
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5438">[ date ]</a>
+ <a href="thread.html#5438">[ thread ]</a>
+ <a href="subject.html#5438">[ subject ]</a>
+ <a href="author.html#5438">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
+mailing list</a><br>
+</body></html>