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 --- .../attachments/20120730/32f0b89e/attachment-0001.html | 13 +++++++++++++ .../attachments/20120730/32f0b89e/attachment.html | 13 +++++++++++++ 2 files changed, 26 insertions(+) create mode 100644 zarb-ml/mageia-discuss/attachments/20120730/32f0b89e/attachment-0001.html create mode 100644 zarb-ml/mageia-discuss/attachments/20120730/32f0b89e/attachment.html (limited to 'zarb-ml/mageia-discuss/attachments/20120730/32f0b89e') diff --git a/zarb-ml/mageia-discuss/attachments/20120730/32f0b89e/attachment-0001.html b/zarb-ml/mageia-discuss/attachments/20120730/32f0b89e/attachment-0001.html new file mode 100644 index 000000000..321e31aa7 --- /dev/null +++ b/zarb-ml/mageia-discuss/attachments/20120730/32f0b89e/attachment-0001.html @@ -0,0 +1,13 @@ +

Hi Olav,

On Jul 29, 2012 8:07 PM, "Olav Vitters" <olav@vitters.nl> wrote:

+> On Sun, Jul 29, 2012 at 07:49:20PM -0400, Michael Hill wrote:
+> > I'm running Cauldron and just performed the UsrMove procedure to
+> > permit installation of updates for the first time in a number of days.
+> > Still, System Settings have not been runnable from the user menu for
+> > many weeks.
+>
+> Works for me. Please give more details.

+

My user menu has been messed up since Cauldron restarted... missing items, different order. I noticed a few weeks ago Suspend was missing and Power Off was in the middle of the menu. Now it's at the bottom where it belongs and Suspend is accessible with the Alt key (Suspend no longer works the way it once did, but now drains the battery).

+ +

About two weeks ago my video driver was killed by an update, so I got the GDM background with the progress spinner but no GNOME Shell. Updating from the console corrected this after a few days.

The System Settings menu pick until recently would try to start from the menu, displaying "System Settings" in the app menu position on the top bar but failing. Now it doesn't even try *that* hard, it just doesn't do anything.  +I would have sworn it could once be launched from the command line, but now it's unrecognized.

+

Is there some way to wipe out my configuration and start from scratch? By re-installing a package, maybe? Otherwise let me know what kind of output is needed to diagnose.

Thanks,

Mike


diff --git a/zarb-ml/mageia-discuss/attachments/20120730/32f0b89e/attachment.html b/zarb-ml/mageia-discuss/attachments/20120730/32f0b89e/attachment.html new file mode 100644 index 000000000..321e31aa7 --- /dev/null +++ b/zarb-ml/mageia-discuss/attachments/20120730/32f0b89e/attachment.html @@ -0,0 +1,13 @@ +

Hi Olav,

On Jul 29, 2012 8:07 PM, "Olav Vitters" <olav@vitters.nl> wrote:

+> On Sun, Jul 29, 2012 at 07:49:20PM -0400, Michael Hill wrote:
+> > I'm running Cauldron and just performed the UsrMove procedure to
+> > permit installation of updates for the first time in a number of days.
+> > Still, System Settings have not been runnable from the user menu for
+> > many weeks.
+>
+> Works for me. Please give more details.

+

My user menu has been messed up since Cauldron restarted... missing items, different order. I noticed a few weeks ago Suspend was missing and Power Off was in the middle of the menu. Now it's at the bottom where it belongs and Suspend is accessible with the Alt key (Suspend no longer works the way it once did, but now drains the battery).

+ +

About two weeks ago my video driver was killed by an update, so I got the GDM background with the progress spinner but no GNOME Shell. Updating from the console corrected this after a few days.

The System Settings menu pick until recently would try to start from the menu, displaying "System Settings" in the app menu position on the top bar but failing. Now it doesn't even try *that* hard, it just doesn't do anything.  +I would have sworn it could once be launched from the command line, but now it's unrecognized.

+

Is there some way to wipe out my configuration and start from scratch? By re-installing a package, maybe? Otherwise let me know what kind of output is needed to diagnose.

Thanks,

Mike


-- cgit v1.2.1