tde-users

users@trinitydesktop.org

20 participants
4181 discussions

by Istvan Gabor

Hello: I have a simple plain text document that contains the following symbols: • − ⋆ ▷ ∘ ◯ ◯ □ In trinity applications (eg kwrite) they are not shown correctly. Instead of the symbols squares are shown. Libreoffice shows the symbols correctly. On another machine which has legacy KDE 3.5.10 the symbols are also shown correctly in kwrite. Whys is this and how can I fix it? I use trinity 14.0.4 in openSUSE 13.2 64 bit. Thanks, Istvan

7 years, 10 months

Re: [trinity-users] r14-xdg-update follies

by Dave Lers

Leslie Turriff wrote: >> Check applications-tdemenuedit.menu for '<Filename>kde-' in >> /var/tmp/tdecache-leslie/r14-xdg-update-validation-test9.txt. > I have attached the above file for review. What directory > would these files reside in? Apparently in ~/.config/menus/applications-tdemenuedit.menu If that is where those files are, running $ ls -lh ~/.config/menus/applications-tdemenuedit.menu/ will let you know if there is a permissions issue. They should be owned by you and have 644 permissions.

7 years, 10 months

Re: [trinity-users] r14-xdg-update follies

by Leslie Turriff

On Friday 03 March 2017 00:52:19 Leslie Turriff wrote: > Recently, when logging into my main ID on my new desktop system, I get > several messages about something called r14-xdg-update. The text of the > first one is > > > The r14-xdg-update script has been run at least once. > > The script is not successfully updating. > > The script will run with each login until corrected. > > Please contact an administrator or take appropriate administrative action > > to correct the problem. The error code is 9. > > Searching the list archive, I found a few references to this script, but > little useful information about it aside from the information that error > code 9 has something to do with file privileges. There seems to be nothing > in the documentation about this script, which seems to perform some sort of > updates to the Trinity configuration. From the effects that it has had on > my system, I would say that there needs to be something written up and > placed into the user doecumentation about this. So far it has wiped out my > desktop settings and recently it made all of my kmail (configuration, > folders and contents) disappear. What do I need to do to fix this? I'm > afraid to log into any of my secondary IDs for fear that they will be > corrupted as well. The vague description of error code 9 gives me little > to go on. What file privileges need to be set, for what files or > directories? What exactly is r14-xdg-update trying to do? > > Leslie I'm also getting this message at login: > Some Trinity R14 XDG compliance updates failed. > Check applications-tdemenuedit.menu for '<Filename>kde-' in /var/tmp/tdecache-leslie/r14-xdg-update-validation-test9.txt. I have attached the above file for review. What directory would these files reside in? Leslie

7 years, 10 months

Porting individual trinity programs to Android

by Philip Ashmore

Hi there. I've got a really great Amarok playlist of songs that I find help me concentrate. I've looked for a means of playing such a playlist on Android without success. If anyone has succeeded in porting a TDE program to Android it would maybe bring this dream a little closer. Please tell me I'm not the only one with such a dream :) Regards, Philip Ashmore

7 years, 11 months

OAuth in KMail?

by dep

greetings, everybody . . . this morning i received a fairly alarming note from my ISP, who apparently farms out its mail handling to yahoo (and yahoo seems to have belatedly gotten interested in security). the note specified that i am not using a sufficiently secure mail client (KMail in TDE) and that in a few weeks OAuth will be required. an admittedly brief search has not produced information as to whether this is something that can be enabled in KMail in TDE or, if so, how to enable it. is this something that has come up before? if so, how was it resolved? and if it hasn't, any solutions? thanks very much. -- dep The shortest distance between you and playing great acoustic guitar: the great new instructional DVDs from Marjorie Thompson, available at www.MarjorieThompson.com

7 years, 11 months

Trinity SSL Certificate Status

by Timothy Pearson

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 I just wanted to let you know that the new TDE site SSL certificates have been installed. They are valid until 2020 so we should be good to go for quite some time. QuickBuild is handled somewhat outside of the TDE project itself, but should also be updated in the next month or so. Thank you all again for helping resolve this issue so quickly! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iFYEARELAAYFAliniqMACgkQLaxZSoRZrGHZzwDeMOYKZ/iiC6ZaMaIVXwsXOo0L pprznl0vuy/M4QDgtInLknauKmFtWc3Gmg8/0SQryDP5f/X/75cYOw== =yNSu -----END PGP SIGNATURE-----

7 years, 11 months

Re: [trinity-users] Trinity SSL Certificates

by Dave Lers

Timothy Pearson wrote: > LetsEncrypt does not appear to be secure enough as it > effectively requires automated certificate installation on the > master servers, and furthermore I expect it to be removed from > as a fully trusted root CA or at least demoted in some way in the > future [3]. I'd suggest a little more research while paying attention to the originating source material (CA's who are losing money). At least one of the FUD sources in your link has been responded to: https://unmitigatedrisk.com/?p=552.

7 years, 11 months

Re: [trinity-devel] Trinity SSL Certificates

by Timothy Pearson

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 > Consider it done. > > Calvin And with that we're good to go! I'll order the replacement certificates shortly, which should reactivate TDE under all major browsers. Thank you all very much for stepping up and helping fix this, I greatly appreciate it! Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iFYEARELAAYFAlimXdwACgkQLaxZSoRZrGEgFQDgp6Kl+GwPIXNiCdDbjTtm0o+l wiT/uPSOWQWX0ADaAjn85+nk3UsGkbp7guXH/3pUc7Ij8kwbMiGeGA== =/HH8 -----END PGP SIGNATURE-----

7 years, 11 months

Trinity SSL Certificates

by Timothy Pearson

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 As some of you may already be aware, StartCom (a major provider of SSL certificates) has repeatedly and intentionally violated the basic rules to be listed as a root CA in most browsers [1] [2]. Unfortunately, TDE used StartCom as its root CA provider in an attempt to lower overall costs; as a result, the main TDE pages, QuickBuild, and other related services will no longer be accessible to the majority of Web clients. We do not have the funds to replace the certificate with a costlier option at this time. LetsEncrypt does not appear to be secure enough as it effectively requires automated certificate installation on the master servers, and furthermore I expect it to be removed from as a fully trusted root CA or at least demoted in some way in the future [3]. Due to the industry-standard security in use, we cannot simply disable HTTPS without disabling access to all TDE sites previously using HTTPS. Furthermore, disabling HTTPS would open TDE users adn visitors to malicious MITM attack, and I am not willing to do this. Our only options come down to either accepting the heavy loss in visitors / traffic that will come from using a self-signed certificate, or attempting to raise the funds required to purchase a new certificate. It should only cost around $200 to obtain a new multi-year certificate covering TDE, so if you can please contribute something toward this goal via our donations page [4]. Again, I apologize for the inconvenience; it is not common for a CA to be delisted and the impact from this has been felt across many sites. Unfortunately, it will only continue to worsen as Chrome (with its 75% market share) is updated by end users over the next few days / weeks. Thank you! [1] https://security.googleblog.com/2016/10/distrusting-wosign-and-startcom.html [2] https://blog.mozilla.org/security/2016/10/24/distrusting-new-wosign-and-sta… [3] http://www.datamation.com/security/lets-encrypt-the-good-and-the-bad.html [4] https://trinitydesktop.org/donate.php -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iFYEARELAAYFAlimAWgACgkQLaxZSoRZrGEmvgDgiRW0d0/yTuzseNQm7of0gzMz WPJSiyQPYpvBKQDgpU4QtQdAQ9ZIhjUBbzNTY/DgBBRmd53/P6QZsQ== =U7kv -----END PGP SIGNATURE-----

7 years, 11 months

TDE NetworkManager frontend not working. Got "unable to perform requested operation". ConsoleKit (rly needed?) and PolicyKit are installed.

by Richard Lamboj

Hello, i can not use the tde network-manager frontend. A Message-Box pops up and says: Unable to save network connection! Potential causes: * Insufficient permissions * NetworkManager not running * DBUS failure Beside that i think the Assistent should not be closed. Both - ConsoleKit and PolicyKit - are installed. And i'm using OpenRC, not systemd on Debian Jessie, with backports enabled. Kind Regards, Richard

7 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users