DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have seen that thread, and several other ones - perhaps I should have explained a bit better in my OP.
I have tried a similar thing before, in Kali, and with a different set of instructions, but I ended up breaking pretty much the whole thing.
Given that I do not want to end up reinstalling again, and that Kali is as I understand based in some capacity on Debian, I want to try and avoid a similar disaster.
So, would you (or anyone else) be kind enough to sanctify those or any other guides?
I shall take my own precautions regardless but it is always nice to have some reassurance from an someone/people more experienced in the world of nix.
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Rep:
I would just reinstall, and be sure not to install KDE. I think in the end you will find that to be faster and much easier. Otherwise there is a very good chance you will break your distro.
If you use aptitude with the -s simulation switch on you can pretest the impact of purging a bunch of kde packages. I am using KDE with Jessie. Suppose I want to switch to LXDE. I would first install LXDE and then try this command.
As you see if I accept that solution then it will immediately purge 128 KDE packages. I can then manually purge the 20+ packages of the second list easily enough and that should remove pretty much all traces of KDE. Using the simulation mode (-s) and running aptitude as a normal user to try out the command before actually executing anything gives you a secure way of seeing the impact of what you want to do.
jdk
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900
Rep:
If you used the command given to you by jdkaye you will cause a situation, and this is by design of the system, that tells you that other packages are now missing things they depend on to work. If anything in that list comes from Gnome then it says to me that on a previous occasion you have removed something that Gnome packages also depend on.
What I would do, if I were you, is open synaptic. Go to the status tab on the left hand side at the bottom., then go up the top of the left hand side and see if there is a line that says "Installed (Auto Removable)". If there is check out what they are (they are probably the Gnome applications). If there is nothing there find kdelibs-bin in synaptic and right click on it and then select "Mark For Complete Removal". Let it remove it and then check your "Installed (Auto Removable"" list and see what's in it. There should only be KDE packages.
That is very strange. What was the exact command you used to get such a response. If you look at my output you'll see that the packages to be purged are pretty much all kde related.
jdk
If you need more to get a better idea please let me know what commands I need to run?
sources.list
Code:
# deb cdrom:[Debian GNU/Linux 7.6.0 _Wheezy_ - Official amd64 NETINST Binary-1 20140712-14:09]/ wheezy main
#deb cdrom:[Debian GNU/Linux 7.6.0 _Wheezy_ - Official amd64 NETINST Binary-1 20140712-14:09]/ wheezy main
deb http://ftp.uk.debian.org/debian/ wheezy main non-free contrib
deb-src http://ftp.uk.debian.org/debian/ wheezy main non-free contrib
deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free
# wheezy-updates, previously known as 'volatile'
deb http://ftp.uk.debian.org/debian/ wheezy-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian/ wheezy-updates main contrib non-free
#Firefox
#deb http://packages.linuxmint.com debian import
#Aircrack-ng
#deb http://ftp.de.debian.org/debian wheezy-backports main
#Ettercap
# deb http://ftp.de.debian.org/debian squeeze main
#Ralink Wireless Firmware
#deb http://http.debian.net/debian wheezy main contrib non-free
#Kernel Headers
deb http://ftp.de.debian.org/debian wheezy main
I had also done a dpkg --add-architecture i386 to install teamviewer as per their website, although I cant remember now if that was before or after I ran the purge command.
---------- Post added 10-25-14 at 10:26 AM ----------
Quote:
Originally Posted by timl
why not set up a VM to mimic your current config. The see what happens when you remove KDE?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.