summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005372.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005372.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/005372.html195
1 files changed, 195 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005372.html b/zarb-ml/mageia-dev/2011-June/005372.html
new file mode 100644
index 000000000..6cf484fd7
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/005372.html
@@ -0,0 +1,195 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] GNOME 2.32 borked
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20GNOME%202.32%20borked&In-Reply-To=%3C4DF240B4.4060904%40roadrunner.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="005421.html">
+ <LINK REL="Next" HREF="005378.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] GNOME 2.32 borked</H1>
+ <B>Frank Griffin</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20GNOME%202.32%20borked&In-Reply-To=%3C4DF240B4.4060904%40roadrunner.com%3E"
+ TITLE="[Mageia-dev] GNOME 2.32 borked">ftg at roadrunner.com
+ </A><BR>
+ <I>Fri Jun 10 18:05:08 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005421.html">[Mageia-dev] perl 5.14.0 should arrive soon
+</A></li>
+ <LI>Next message: <A HREF="005378.html">[Mageia-dev] GNOME 2.32 borked
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5372">[ date ]</a>
+ <a href="thread.html#5372">[ thread ]</a>
+ <a href="subject.html#5372">[ subject ]</a>
+ <a href="author.html#5372">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Just updated and rebooted a system which was last rebooted Jun 7, and
+both GDM and KDM fail to log into my GNOME DE with a greyish popup
+saying &quot;failed to load your GNOME session&quot;.
+
+/var/log/gdm/0.log shows a segfault backtrace in fglrx, but this could
+be a red herring, since KDE starts fine for the same user.
+
+The GNOME configuration for the user seems to be OK, because booting an
+earlier Mageia beta logs into the DE just fine.
+
+I've avoided installing GNOME3 by using urpmi --keep, but maybe some
+GNOME3 package slipped through that doesn't depend on the ones that want
+to remove 2.32 ?
+
+Anybody else ?
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005421.html">[Mageia-dev] perl 5.14.0 should arrive soon
+</A></li>
+ <LI>Next message: <A HREF="005378.html">[Mageia-dev] GNOME 2.32 borked
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5372">[ date ]</a>
+ <a href="thread.html#5372">[ thread ]</a>
+ <a href="subject.html#5372">[ subject ]</a>
+ <a href="author.html#5372">[ 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>