plasma-desktop inconvenient...

273 · 11-15-2015, 09:16 AM

You may use either -- I prefer apt-get as I have always used it.
I think the rule of thumb is to use only one of them if one wishes to avoid issues. If I were you I would read up on aptitude's attitude to removing packages and find out why it wants to do it and whether it is compulsory to remove them.

TobiSGD · 11-15-2015, 10:20 AM

So you are down to one package that makes problems. This is not that uncommon in Sid and I would recommend to wait a couple of days and try it again, it is possible that at that point the dependency issues are fixed.

un1x · 11-15-2015, 01:51 PM

http://s10.postimg.org/jc4vcdzxl/task_manager.png

3 task managers

how to fix that ?

TobiSGD · 11-15-2015, 06:58 PM

I am not using KDE's panel, but can't you just open the panel settings and delete two of the task bars?

un1x · 11-16-2015, 08:58 AM

not that easy !

Quote:

just open the panel settings and delete two of the task bars?

some 'expert' on kde plasma-desktop ?

luvr · 11-16-2015, 11:40 AM

Quote:

Originally Posted by TobiSGD

So you are down to one package that makes problems. This is not that uncommon in Sid and I would recommend to wait a couple of days and try it again, it is possible that at that point the dependency issues are fixed.

I agree with TobiSGD. This type of dependency issues is part of the "contract" when you run Debian testing. It sometimes happens when a set of packages is in transition, i.e., it is in the process of being upgraded, but not all package upgrades have been made available just yet. Once the complete set of upgrades becomes available, the dependencies will get automagically resolved.

In my experience, it's a bad idea to try and resolve the issues yourself; you will almost certainly do more harm than good if you do. Just wait for a few days, and then retry the upgrade. Of course, KDE is a massive piece of software, so it may take a little longer until all updates are prepared, but the Debian developers will eventually get there.

un1x · 11-16-2015, 02:38 PM

I need to erase .kde ( plasma-desktop) asap some help please !

TobiSGD · 11-16-2015, 02:53 PM

What do you mean with .kde? If it is the KDE configuration directory the just delete it:

Code:

rm -rf ~/.kde

At best do it when not logged in to KDE wit that user.

un1x · 11-16-2015, 03:29 PM

apologize for being so newbie

click on 3 lines or hamburger (bottom corner) more settings >>> remove panel >>> then click on desktop >>> add panel >>> default or empty

goumba · 11-18-2015, 03:45 AM

Quote:

Originally Posted by un1x

apologize for being so newbie

click on 3 lines or hamburger (bottom corner) more settings >>> remove panel >>> then click on desktop >>> add panel >>> default or empty

Why are you even using sid if you are admittedly a newbie?

What are you trying to accomplish with the above? If it's a default KDE panel, remove .kde directory as directed above by TobiSGD (which was an answer to your question as to how to remove it).

* Log out
* From a VT, another desktop or window manager, follow TobiSGD's instruction to remove .kde.
** This prevents any configuration files being rewritten while you are logged in. It may not be totally necessary, but I tend to do this to be on the safe side.
* Log in to Plasma, and a default configuration will be created.

un1x · 11-20-2015, 09:10 AM

again...

what to use ???

aptitude update && aptitude upgrade

or

aptitude full-upgrade

*********************************************************

Code:

#  aptitude update && aptitude safe-upgrade

No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

Code:

# aptitude full-upgrade
The following packages will be upgraded: 
  libetonyek-0.1-1 openjdk-7-jre openjdk-7-jre-headless 
3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 40.4 MB of archives. After unpacking 396 kB will be used.
Do you want to continue? [Y/n/?]

thanks !

273 · 11-20-2015, 11:25 AM

If you are running Sid then you should run a full-upgrade -- otherwise look into running Debian Stable, Ubuntu LTS or Mint LTS.
Sid is "unstable" and will break functionality from time to time, though this can be avoided by careful updates and. Sometimes not doing a full upgrade, because that is what it is designed to do.
I may be wrong but I would consider it almost impossible to support a system which took the safe upgrade route with Sid -- how on earth is one to know what the libraries were when Sid was first installed?

TobiSGD · 11-20-2015, 05:55 PM

Just to clarify: apt-get upgrade and aptitude upgrade will upgrade all installed packages, unless the upgrade process would pull in packages that are currently not installed.
apt-get dist-upgrade and aptitude full-upgrade do not have this limitation.
That means that packages with a change in dependencies, for example due to an added dependency or due to a package split in one of the dependencies, can not be upgraded with the upgrade command, but only with the dist-upgrade/full-upgrade command. For this reason users of Testing and Unstable should always use dist-upgrade/full-upgrade.
By the way, the respective man-pages explain this also, as a user of Testing/Unstable you should really read them.