Hello
PPL.
On my second Update of the system I have found the issue that is the main issue on your machine problems.
- 1
So how we going to be smarter ?
Take screen shot from the Upgrade from synaptic , save it to your Desktop ,then install the packages one by one
and see what are the Dependences for any package that you about to install on your machine.
when you will come across the Dependences of the U.E customization DO NOT INSTALL THIS PACKAGE!!
all the rest of the packages can be installed on your system / just not the packages that will Delete the U.W customization.
Compiz = will Delete your U.E Customization!OK to get the update/upgrade in the safe way you can make it easy to do.HOW?
well you will have like 92 updates/upgrades from KDE , then just search in synaptic for "kde",
Then mark all the updates/upgrades in one time = package after package not full all in one mark.
First I will go to the Kernel alone for upgrade the Kernel to 2.6.35.14 = 5 packages,
Then Restart the machine ,and go on with the rest of the update / upgrades that you have there.
The impotent thing will be to look into the upgrade process with - upgrade/To be installed.
- 2
Then when we see that all cool there and the package of U.E Customization is not there we can prosed with the process of the installation.
one more point here for you is with few packages under the same name like:
python,ttf,apt,KDE,Gnome and so on - you can find them under the same search in synaptic.
The packages that will remain not install will be:
- 3
Let me add some more info for you on getting this process with easy way.
in synaptic (down left side), you can use the Filters to see After reload,
mark all upgrade the packages for upgrade.
there you can change the Filters to Upgrade packages - this will show the packages to be upgrade.
Now you can mark one by one for upgrade - just watch out from compiz packages DO NOT INSTALL THEM.
- 4
No we can see the Compiz packages that will be left.
- 5
The last thing that I will add to this post is about crash in the -
update-apt-xapian-index (Debian index packages).
You can Edit the file and end this bug on your machine with the easy way to go.
Go to => /etc/cron.weekly/apt-xapian-indexopen the Editor that you like to work with an Edit the file to look like this one:
#!/bin/sh
CMD=/usr/sbin/update-apt-xapian-index
# ionice should not be called in an virtual environment
# (similar to man-db cronjobs)
egrep -q '(envID|VxID):.*[1-9]' /proc/self/status || IONICE=/usr/bin/ionice
# Check if we're on battery
if which on_ac_power >/dev/null 2>&1; then
on_ac_power >/dev/null 2>&1
ON_BATTERY=$?
# Here we use "-eq 1" instead of "-ne 0" because
# on_ac_power could also return 255, which means
# it can't tell whether we are on AC or not. In
# that case, run update-a-x-i nevertheless.
[ "$ON_BATTERY" -eq 1 ] && exit 0
fi
# Rebuild the index
if [ -x "$CMD" ]
then
if [ -x "$IONICE" ]
then
nice -n 19 $IONICE -c 3 $CMD --update --quiet
else
nice -n 19 $CMD --update --quiet
fi
fi
Good Luck to you all.