On Tuesday 19 of August 2014 07:41:23 Robert Peters wrote: Package ksmserver-trinity is installed? -- Slavek

I installed TDE on Ubuntu based Mint 15 + Mate. I had a similar problem with TDE menu item missing from MDM, a Mint config app that kept auto starting, and Mate autostarting when I logged out of TDE. I removed MDM and Mate base apps, and bit-by-bit removed other suspect parts of Mate until the problems stopped. I believe I used startx for a while and then added TDM with SAK manually disabled in kdmrc before the first logout. I did not have those problems running TDE in Mint + Xfce. On that installation I was able to leave Xfce fully intact with no such problems. Mint continued to have a nasty problem with refusing to turn off the computer after shutdown or complete the reboot cycle. That has nothing to do with TDE, of course. On 8/19/14, Robert Peters <robertpeters9(a)gmail.com> wrote:

On 23 August 2014 19:04, Slávek Banko <slavek.banko(a)axis.cz> wrote: Debian 201403 MATE 64-bit

On 24 August 2014 18:31, Robert Peters <robertpeters9(a)gmail.com> wrote: Fixed part of it :-) Changed Debian's and Slavek's sources from wheezy to jessie, upgraded binutils, installed libr0, installed some favorite TDE apps (R14). Q: now should I upgrade the other Debian packages to jessie? At what point do I use dist-upgrade? Robert

You should not run Stable and Testing (in this case Wheezy and Jessie) on the same system. If you must use Testing type packages then you are much better off either running a full Testing system or running Stable with Backports if the packages you need are in Backports. From the Debian manpage " upgrade upgrade is used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list. Packages currently installed with new versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. An update must be performed first so that apt-get knows that new versions of packages are available. dist-upgrade dist-upgrade in addition to performing the function of upgrade, also intelligently handles changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones if necessary. The dist-upgrade command may therefore remove some packages. The /etc/apt/sources.list file contains a list of locations from which to retrieve desired package files. See also apt_preferences(5) <http://manpages.debian.org/cgi-bin/man.cgi?query=apt_preferences&sektion=5&apropos=0&manpath=Debian+7.0+wheezy&locale=> for a mechanism for overriding the general settings for individual packages." If there are no new packages (in other words packages not already installed in any version) required you don't have to use dist-upgrade, if there are new packages required you do have to use dist-upgrade. On 25 August 2014 23:36, Robert Peters &lt;robertpeters9(a)gmail.com&gt; wrote: