[ale] had a terrible time installing lubuntu-desktop

Richard Faulkner rfaulkner at 34thprs.org
Fri Feb 25 08:36:05 EST 2011


That´s why we do all of this type of work in VMs my friend or on a test
box!  : )

Experimenting on a live subject is a very dicey proposition........glad
you got it back (more or less)........cheers!    


-----Original Message-----
From: Ron Frazier <atllinuxenthinfo at c3energy.com>
Reply-to: Atlanta Linux Enthusiasts <ale at ale.org>
To: Atlanta Linux Enthusiasts <ale at ale.org>
Subject: [ale] had a terrible time installing lubuntu-desktop
Date: Thu, 24 Feb 2011 23:39:13 -0500


Based on recommendations to try different desktops on the LinuxBasix 
podcast, I decided to try LXDE.  I was under the impression that it and 
GNOME could run side by side and that you could select the one you want 
at boot.  I installed lubuntu-desktop from the Ubuntu Repositories.  
Then, things went down hill.  At one point in the install, it asked 
which should be the default window manager.  I chose lxdm, I think.  
After rebooting a couple of times, something was driving the CPU to 85% 
all the time.  It turns out to be lxdm-binary.  Apparently the GNOME 
program and the LXDE program were conflicting.  This was occurring 
whether I boot into GNOME or LXDE.  I used System Monitor to kill the 
process and decided to figure it out later.

In order to customize the desktop, I deleted the default panels and put 
back some new blank ones, and then couldn't find a way to get the shut 
down button back, nor the trash can.  They are not in the add to panel 
menu.  Frequency scaling was inop, and I had no way (that was obvious) 
to get to my wireless setup and log into my router.  I booted back into 
GNOME, and decided to use Synaptic to completely remove lubuntu-desktop, 
which I did, then rebooted.  The lxdm-binary program is still there, and 
still conflicting with GNOME.  I used System Monitor to kill the 
process.  I then used GKSU to start Nautilus and search for anything 
with LXDM in the name.  I delete them all and reboot.  Now, it APPEARS 
that GNOME is back to normal.  At least the CPU is idling around 0% when 
I'm not doing anything, like it should be.  I have no idea if everything 
is working as it should behind the scenes, or if extra stuff is running.

I learned one thing though.  I will NEVER try that again unless it's in 
a VM.  If I choose to install something like another desktop, I'll make 
sure I have an up to the minute backup.  If you guys think there's 
anything in particular that I need to check in the system configuration, 
please let me know.

Sincerely,

Ron



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20110225/a1059440/attachment.html 


More information about the Ale mailing list