tde-devels February 2017

devels@trinitydesktop.org

11 participants
8 discussions

Re: [trinity-devel] No USB storage insertion notifications (was: [users] External drive gets mounted twice)

by Felix Miata

deloptes composed on 2017-02-27 18:47 (UTC+0100): > Felix Miata wrote: ... >> I updated Jessie, including bpo 4.9.2, and there's still no >> notification, plus dmesg is loaded with i915 driver segfaults. ... > What are the kernel versions there. AFAIR it is kernel (usb) -> udev -> > dbus. Do you have systemd enabled? I think this information could help not > only in your case but also in the case of Thierry. If I counted right, my previous email reported 10 different installations across 4 64-bit PCs, 9 openSUSE, 1 Jessie. All are inextricably dependent on systemd. The only ones that work right are the 2 oldest openSUSE (42.1), and only with KDE3, which means nothing I've yet tested with a kernel newer than 4.1.36, or with 14.0.x TDE, works. Of the 10, I checked for udisks versions on several, and found both udisks and udisks2 installed on each. > On my debian tde 14.1 with kernel 4.9 all works fine.-- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

7 years, 8 months

digikam 0.9.6 image editor crashes when selecting area

by Istvan Gabor

Dear Trinity developers: I use openSUSE 13.2 and Trinty TDE R14.0.4 64 bit. Digikam version is trinity-digikam-0.9.6-14.0.4_1.oss132.x86_64. Digikam crashes when in image editor I right click the images or try to select area. It does not occur with all images, only if the resolutions or file size is over a limit, though I don't know the limit. It occurs with jpg file 3264x2448 resolution ~1.8 MB, but it doesn't occur if I downsize this image to 1500x1125 ~500 KB. I found that a similar (same?) problem was reported in 2015: Digikam 0.9.6 selection problem http://trinity-users.pearsoncomputing.net/?0::9315 I would appreciate any help with fixing this problem. Thanks, Istvan

7 years, 8 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, 9 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) iFYEARELAAYFAlimAXYACgkQLaxZSoRZrGG6QQDeObweyASWhjs/USiO6Nm05CcH C20FUSd8bT7Y7wDdGKueJfay8/HacDBlPw+u2WItBSpRs3geLoPLSw== =RdsZ -----END PGP SIGNATURE-----

7 years, 9 months

[trinity-devel] added trinity to stretch -> purge lightdm adds 22 packages ???

by Felix Miata

Is this "need" for more libs on attempt to clean installation of unnecessaries expected? Attachment shows installed trinity packages and shellcap from attempt to purge no longer needed lightdm*. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

7 years, 9 months

"wrong" ISO image size to be used in VirtualBox

by Nicola Ferrari (#554252)

Hi list! I recently experienced a problem with the TDE Ubuntu 14.04 amd64 iso image: it wasn't accepted as VM cd image in virtualbox. To exclude a vbox problem, I wrote to their mailing list: one user told me that, an iso image, to be consired a standard image, should have its size dividable by 2048. [1] I just had a try seeking the image with 2048 as block size and everything is working properly. Maybe images in the future should be "burned" with that block size? Thanks! Nick [1] https://www.virtualbox.org/ticket/14530 -- +---------------------+ | Linux User #554252 | +---------------------+

7 years, 9 months

Translations

by Sebastião Guerra

Hi, How can I help with translations?

7 years, 9 months

[Patches] Enhancement of test/check building

by Fat-Zer

Good day, A long time ago I (kinda) promised to do something good on the testing support for tdelibs with cmake. I'm sorry I protracted it so much. But as it sad it's better late then never, so I want to present a series of patches to fix/add/restore/enhance/whatever test support in tdelibs. Long story short: the repository is located here: https://github.com/Fat-Zer/tdelibs/tree/fix-check (branch fix-check) Note that cmake submodule has a different link due to it required some modifications too There were already some workarounds for tdeui and tdeabc, but they had several problems: - checks executables were added to "all" target, so they were build unconditionally - tests were run during build phase (which is confusing and wrong) - no test statistics etc What the patch set features: - Add EXCLUDE_FROM_ALL flag for tde_add_library macro - New macro tde_add_check_executable - add tests from dcop/tdecore/tdeui/tdeio/tdeabc/tdewallet - a fix in tdeio against mimemagic (fixes one check application) - 40+ automated tests (mostly of base features which won't likely fail) but anyway IMHO it's nice to have them. How to use: To build tests/check run "make check"; To run automated tests run either "make test" or "ctest"; To run specific tests e.g. for tdecore use "ctest -R tdecore" (note that "tdecore" is just a substring of a test name ) To see verbose output of tests add -V flag "ctest -V -R tdecore". For more information see cmake documentation about ctest and cmake add_test macro. No automated test require nor X session nor a running tde session, but if run inside a such session they may interact with it. About tde_add_check_executable cmake macro: The macro is mostly a tde_add_executable with a redused set of arguments, but except of adding executable target to the "all" it adds them to a special custom target "check". As of specific of test executables (which are mostly one-source-file-based) it doesn't require the SOURCE section, instead of which it globs the files based on the target name. Also it has a TEST argument to automatically add a test out of given file.

7 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels February 2017