On Wednesday 19 of November 2014 23:06:00 Timothy Pearson wrote:
On Tuesday 18 of November 2014 23:06:52 Lisi Reisz wrote:
On Tuesday 02 September 2014 16:20:55 Slávek Banko wrote:
Dne út 2. září 2014 Lisi Reisz napsal(a):
Slávek -
Should this be:
deb http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14 deb-src http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
for Linux Mint 17?
Thanks, Lisi
P.S. Yes, I know I could suck it and see, but I am struggling so
much
with being unable to see the awful MATE that I want to make as few errors as possible while trying to render Mint visible - and
therefore
usable.
Yes, Mint 17 is based on Ubuntu Trusty, so given APT sources should
work
correctly.
I have been struggling with the awful Linux Mint and MATE ever since. I felt that I must move beyond my comfort zone. Debian and TDE is so easy and so familiar. So for my new box for playing streaming media on my television I installed Linux Mint 17 with Mate.
I have made myself give it a fair chance. But I can stand it no longer. So I bit the bullet, edited my sources.list, updated and tried to install TDE 14.
This is the result:
<quote> The following packages have unmet dependencies: tdeprint-trinity : Conflicts: foomatic-db-compressed-ppds but 20140410-0ubuntu1 is installed. The following actions will resolve these dependencies:
Remove the following packages:
foomatic-db-compressed-ppdsKeep the following packages at their current version:
kubuntu-desktop-trinity [Not Installed]</quote>
Help!!
I hope that I have copied and pasted enough. As I say, I am struggling. Mate, anyhow in its Linux Mint version, is almost invisible. (To me, at any rate. But I can't use anyone else's eyes. ;-) )
I could, of course, simply wipe the lot and install my beloved Wheezy and TDE 3.13.2.2. But that would be defeatist.
Thanks, Lisi
To return to the beginning of issues:
Definition of conflict with foomatic-db-compressed-ppds I see as a big problem. Many other DE has it as a dependency and TDE because of this makes it quite complicated concurrent installation with another DE.
If I understand well, the only effect is that with this package does not work the setup printer queue in TDE Control Center? However, the user can still set up the printer using the CUPS web interface. It is really useful to define this conflict package?
I thought we had a bug report open on tdeprint not supporting compressed PPDs but now I can't find it. If you can't find it either then a new report should be filed.
Regarding the conflict, the problem is tdeprint will silently fail if the compressed PPDs are installed (it thinks there are no PPDs on the system in this case). At minimum an error message stating that the uncompressed PPDs need to be installed should be added to tdeprint so that the user knows *why* tdeprint is failing. There should also be a manual "Rebuild Driver Database" button added somewhere in tdeprint.
I wonder how hard it would be to add compressed PPD support. It seems that tdeprint would just need to use the gzip ioslave instead of reading each PPD directly...
Tim
Corresponding bug is 697: http://bugs.trinitydesktop.org/show_bug.cgi?id=697
If I remember correctly, the problem is that PPD is not compressed as individual gzip files, but "embedded" in the driver command that is used to obtain a specific ppd. See: /usr/sbin/lpinfo --make-and-model '.' -m