tde-devels

devels@trinitydesktop.org

8 participants
3849 discussions

ACPIAC k(t)control module in TDE?
by David C. Rankin 16 May '18

16 May '18

Tim, all, This is a tangential question on whether TDE has included an acpiac configuration module for specifying event-handling for say laptop power-button (suspend or off) as well as lid closed, etc. This is prompted by the trend away from acpi (with the configuration for event handling in /etc/acpi/handlers.sh) to acpiac which has a dearth of documentation and limited user-information. Evidently, plasma, gnome and xfce have configuration widgets for it. K3 has none (aside from the monitor DPMS control -- which isn't related). If TDE has an implementation, I'd love to see the commit and see how you did it, and where you put the interface. If TDE doesn't have an interface yet, well throw it on the wishlist heap -- as it looks like we will all have to deal with this power-interface in the near future -- it's code feeds into the kernel -- so it's coming. Short list of info links: https://www.acpica.org/documentation what it is: https://acpica.org/sites/acpica/files/ACPI-Introduction.pdf or the API/Programming Reference: https://acpica.org/sites/acpica/files/acpica-reference_18.pdf OS-Dev wisdom: https://wiki.osdev.org/ACPICA -- David C. Rankin, J.D.,P.E.

1 1

TDE for Ubuntu 18.04 LTS - Bionic Beaver
by MLR 15 May '18

15 May '18

Hi. I am still using 12.4 and would like to upgrade to 18.4 in a few weeks. Will there be a TDE release for 18.4 soon? I still mourn the great KDE 3 and love TDE. :) Best regards Tom

2 2

Donation to TDE
by Alexandre Couture 29 Apr '18

29 Apr '18

Hi, I've just made a donation to the TDE project, but I am however concerned about a detail: I see that most commits are from Michele Calgaro and Slavek Banko, but I am not sure if they receive a part of these donations, to thank them for their time. I do understand that Timothy Pearson is providing some infrastructure for TDE, and has problably less time to work on TDE or interest nowadays, but I think that it would make sense to have some parts of the donations directed to the active developers. Can someone clarify this please? (Of course, by them way, don't forget to do a little donation to TDE, to see it up and running) Thank you and have a great day! -Alexandre

1 0

tde-open
by wofgdkncxojef＠gmail.com 21 Apr '18

21 Apr '18

what about my simple proposal for tde-open "what about having an alias for "kfmclient exec" to tde-open? There is kde-open, mate-open, gnome-open... tde-open would be a logical expectation." https://bugs.trinitydesktop.org/show_bug.cgi?id=2816 a simple wrapper script #!/bin/bash kfmclient exec "@" in /opt/trinity/bin named tde-open should do the trick.....

1 0

older bugs
by deloptes 21 Apr '18

21 Apr '18

Can you look into those bugs and why we do not clean up a bit? https://bugs.trinitydesktop.org/show_bug.cgi?id=267 https://bugs.trinitydesktop.org/show_bug.cgi?id=630 This is definitely solved through the upgrade to gnupg2 https://bugs.trinitydesktop.org/show_bug.cgi?id=1090 And what happened to my request https://bugs.trinitydesktop.org/show_bug.cgi?id=2691 I need to learn managing git branches to be able to follow :) regards

1 0

knode gpgp signed messages
by deloptes 13 Apr '18

13 Apr '18

Hi, I wonder if you have ever seen signed messages in knode appear like in kmail with nice header. ATM I see the signature as attachment and when try to open it throws gpg error. IMO the problem is in Module::prepareMessageForDecryption, but looking into the code I doubt it was ever working Opening the signature seems to be another issue -> perhaps threating attachment or so via some part. I just generated a key for deloptes(a)gmail.com and try sign this message and it says I have not configured the key for signing. thanks regards

1 4

bug 2729
by deloptes 11 Apr '18

11 Apr '18

Hi, regarding https://bugs.trinitydesktop.org/show_bug.cgi?id=2729 I am wondering why m_config.readBoolEntry( "Empty", true ) would report false, when in the config file it is still true and m_config.sync() was called. Any ideas? regards

2 4

bug 2729
by deloptes 11 Apr '18

11 Apr '18

1 0

how to prevent a hugs/freebsd fiasco in trinity
by wofgdkncxojef＠gmail.com 12 Mar '18

12 Mar '18

Hi every one. I'm sure you all know about the storm about the new code of conduct in freebsd. (you need to ask consent in advance before sending virtual hugs.... etc) This is happening, because their governing structure is a committee. They are making an experiment in politics, with rules and votes and consensus etc.... You can easily avoid this, by just having an enlighten dictator. A bit like Torvalds with linux. In the Linux project, there is no committee and votes and politics. Linus has the final word. An open source project is not like in real life, if you think the benevolent dictator is a dick, you just tell him and fork. So, trinity should remain a dictatorship. Even if the project got big. I'm assuming the dictator is petersons. And when he leaves, he must appoint a successor. If that ever turned to shit, people would have to decide to fork then. (Roman emperor Caligula once, ordered his men to collect seashells) A common mistake with projects/businesses, is that the founders don't think through about what happens after they are gone. hugs :P

3 3

Re: [trinity-devel] how to prevent a hugs/freebsd fiasco in trinity
by Alexis PM 11 Mar '18

11 Mar '18

Hello "Physical contact and simulated physical contact (e.g., textual descriptions like "*hug*" or "*backrub*") without consent". Agree with you that the FreeBSD's New Code of Conduct overreaches out of place. Desagree with you that this "clarifies" that horizontal organizations are bad and that software projects work better with a vertical structures with a benevolent dictator. But where FreeBSD fails, similar organizated projects as Debian or Gentoo work fine. There are long-standing free software projects with vertical organizations but also ones with horizontal organizations. What is failing in Trinity is the number of developers and collaborators, and this will not be changed by a organization modification, additionally I think that a vertical organization with censoring dictators tends to discourage potential collaborators. The praiseworthy Slávek/Timothy/others' dedication can be recognized without creating censoring or hierarchical figures. Likewise, the continuity after the disappearance of some person (exchange of passwords,...) can be guaranteed without the need to create vertical organizations. If a horizontal organization guaranteed the future of the Trinity project, it would be the first person to sign it even if it touches me the lowest post in the hierarchy, but that is not the case. Affectionate hugs to everyone! :) ________________________________ De: "wofgdkncxojef(a)gmail.com" <wofgdkncxojef(a)gmail.com> Para: trinity-devel(a)lists.pearsoncomputing.net Enviado: Sábado 10 de marzo de 2018 23:35 Asunto: [trinity-devel] how to prevent a hugs/freebsd fiasco in trinity Hi every one. I'm sure you all know about the storm about the new code of conduct in freebsd. (you need to ask consent in advance before sending virtual hugs.... etc) This is happening, because their governing structure is a committee. They are making an experiment in politics, with rules and votes and consensus etc.... You can easily avoid this, by just having an enlighten dictator. A bit like Torvalds with linux. In the Linux project, there is no committee and votes and politics. Linus has the final word. An open source project is not like in real life, if you think the benevolent dictator is a dick, you just tell him and fork. So, trinity should remain a dictatorship. Even if the project got big. I'm assuming the dictator is petersons. And when he leaves, he must appoint a successor. If that ever turned to shit, people would have to decide to fork then. (Roman emperor Caligula once, ordered his men to collect seashells) A common mistake with projects/businesses, is that the founders don't think through about what happens after they are gone. hugs :P --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels