Hi all!
I'm (again) in the process of optimizing my laptops power consumption. I noticed that "tdepowersafe" consumes ~ 2.5% of all CPU cycles - this is more than Xorg (1.6%) but less than htop (6.3%). So my question is: does tdepowersafe do constant polling? IMO it should take almost no CPU cycles (<1%)?
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Hello All,
Due to the rebranding that happened on 9/18, the URL will need to be updated (Although the old mirror.nasutek.com will work for now, I don't know how long ill keep that domain for, possibly one more year) to mirror.wiseglobalsolutions.com
NasuTek Global Enterprises is now known as Wise Global Solutions.
Let me know if you have any questions.
Thanks
Michael Manley – Founder, CEO, and Chief Architect
Wise Global Solutions
CONFIDENTIALITY NOTICE: This email, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Effective August 1, 2025, email addresses ending in @ntge.net and @nasutek.com will be discontinued. Going forward, only @wisegs.net email addresses will be supported. Please update your contact information to reflect the new Wise Global Solutions domain (@wisegs.net) before the deadline to ensure continued communication with Wise Global Solutions.
TDE devs,
I passed this along to Yasuhiko for openSUSE kde3, it may also be something
that TDE wants to patch as well:
========== original message ============
The current rust.xml katepart syntax file does not highlight alerts like
TODO, FIXME, etc. in the comments. The katepart/syntax file needs to be
updated to include the katepart/syntax/alerts.xml file.
A patch to do so is:
diff -ruNb a/syntax/rust.xml b/syntax/rust.xml
--- a/syntax/rust.xml 2015-10-28 15:38:53.000000000 -0500
+++ b/syntax/rust.xml 2024-09-10 08:53:59.108745900 -0500
@@ -323,10 +323,14 @@
<RegExpr String="U[0-9a-fA-F]{8}"
attribute="CharEscape" context="#pop"/>
<RegExpr String="." attribute="Error" context="#pop"/>
</context>
- <context attribute="Comment" lineEndContext="#pop"
name="Commentar 1"/>
+ <context attribute="Comment" lineEndContext="#pop"
name="Commentar 1">
+ <LineContinue attribute="Comment" context="#stay"/>
+ <IncludeRules context="##Alerts" />
+ </context>
<context attribute="Comment" lineEndContext="#stay"
name="Commentar 2">
<DetectSpaces/>
<Detect2Chars char="*" char1="/" attribute="Comment"
context="#pop" endRegion="Comment"/>
+ <IncludeRules context="##Alerts" />
</context>
</contexts>
<itemDatas>
@@ -348,6 +352,7 @@
<itemData name="Macro" defStyleNum="dsOthers"/>
<itemData name="Attribute" defStyleNum="dsOthers"/>
<itemData name="Lifetime" defStyleNum="dsOthers" bold="1"/>
+ <itemData name="Alert" defStyleNum="dsAlert"
spellChecking="false"/>
<itemData name="Error" defStyleNum="dsError"/>
</itemDatas>
</highlighting>
--
David C. Rankin, J.D.,P.E.
Michele, Slavek, All,
I just ran across a new bug on openSUSE Tumbleweed where the sftp_kio is
completely broken. I suspect this is the result of the new openssh package and
perhaps option changes, etc...
It's no little issue, attempting to connect in konqueror, kate, kwrite,
etc.. with sftp://host/path/to/whatever -- coredumps.
This slunk in sometime in the past week or so along with new versions of
openssh. I don't have smoking gun evidence it is openssh -- but that is my
best guess based on recently updated packages. Tumbleweed has openssh-9.8p1
built last Friday.
Let me know if you see this in TDE, and if you don't, be on the lookout for
it when openssh updates.
--
David C. Rankin, J.D.,P.E.
Here is the the response from Yasuhiko, he updated kdelibs applying the patch
so the syntax highlights for Alerts are activated in the rust.xml syntax file.
I believe what he says below is that the openeSUSE KDE3 uses the sams May 19,
2020 syntaxt files as TDE, so TDE can apply the patch as-is to activate the
Alert highlighting in rust comments.
-------- Forwarded Message --------
Subject: Re: Add Alerts (FIXME, TODO, etc..) to rust katepart/syntax/rust.xml
Date: Thu, 12 Sep 2024 14:53:58 +0900
From: Yasuhiko Kamata <belphegor(a)belbel.or.jp>
Organization: Bel Bel Network, Japan.
To: suse-kde3 <kde3(a)lists.opensuse.org>
CC: David C. Rankin <drankinatty(a)gmail.com>
Hello,
Ok, updated kdelibs3.
It will be available soon.
After the update in May 19 2020, syntax rule files used by kdelibs3
is the exact same files provided by tdelibs (as shown in OBS,
https://build.opensuse.org/package/show/KDE:KDE3/kdelibs3
-> tdelibs-kate-data.git-**.tar.bz2).
Therefore, the attached patch can be used as-is on the tdelibs side.
Thanks,
On Wed, 11 Sep 2024 11:15:02 -0500
"David C. Rankin" <drankinatty(a)gmail.com> wrote:
> On 9/11/24 1:28 AM, David C. Rankin wrote:
> > Yasuhiko,
> >
> > The current rust.xml katepart syntax file does not highlight
> > alerts like TODO, FIXME, etc. in the comments. The katepart/syntax
> > file needs to be updated to include the katepart/syntax/alerts.xml
> > file.
> >
> > A patch to do so is:
> >
> > diff -ruNb a/syntax/rust.xml b/syntax/rust.xml
> > --- a/syntax/rust.xml 2015-10-28 15:38:53.000000000 -0500
> > +++ b/syntax/rust.xml 2024-09-10 08:53:59.108745900 -0500
> > @@ -323,10 +323,14 @@
> > <RegExpr String="U[0-9a-fA-F]{8}"
> > attribute="CharEscape" context="#pop"/>
> > <RegExpr String="." attribute="Error"
> > context="#pop"/> </context>
> > - <context attribute="Comment" lineEndContext="#pop"
> > name="Commentar 1"/>
> > + <context attribute="Comment" lineEndContext="#pop"
> > name="Commentar 1">
> > + <LineContinue attribute="Comment"
> > context="#stay"/>
> > + <IncludeRules context="##Alerts" />
> > + </context>
> > <context attribute="Comment"
> > lineEndContext="#stay" name="Commentar 2">
> > <DetectSpaces/>
> > <Detect2Chars char="*" char1="/"
> > attribute="Comment" context="#pop" endRegion="Comment"/>
> > + <IncludeRules context="##Alerts" />
> > </context>
> > </contexts>
> > <itemDatas>
> > @@ -348,6 +352,7 @@
> > <itemData name="Macro"
> > defStyleNum="dsOthers"/> <itemData name="Attribute"
> > defStyleNum="dsOthers"/> <itemData name="Lifetime"
> > defStyleNum="dsOthers" bold="1"/>
> > + <itemData name="Alert"
> > defStyleNum="dsAlert" spellChecking="false"/>
> > <itemData name="Error"
> > defStyleNum="dsError"/> </itemDatas>
> > </highlighting>
> >
> > Can that be applied to the system wide rust.xml in
> > /opt/kde3/share/apps/katepart/syntax/rust.xml so that it is
> > available?
> >
>
> Also,
>
> When you have time to apply the patch, can you post the link for
> the patch in the openSUSE build so TDE can reference it. Thank you!
>
> --
> David C. Rankin, J.D.,P.E.
--
Yasuhiko Kamata
E-mail: belphegor(a)belbel.or.jp
--
David C. Rankin, J.D.,P.E.
3111 Skyline Dr.
Nacogdoches, Texas 75965
david(a)rankinlawfirm.com
www.rankinlawfirm.com
Michele, Slavek, All,
On the bleeding edge in openSUSE Tumbleweed, I'm seeing Gtk icons in
kmenuedit with many in the "System icons -> Application" list just named "org"
(which of course breaks trying to use them)
Here is a screenshot of what I see:
https://paste.opensuse.org/pastes/31a073a6794f
Likely this is an issue introduced recently with Gtk4 or the like where
they have buried blobs being org.whatever.gnome.something config tree names
and it looks like kmenuedit is only able to grab the "org" part. (this is just
an educated GUESS on my part)
(oops sent to pearsoncomputing.org first -- and that rejects me now for some
reason, even though I still get bug info from it?)
=== Update! ===
Fortuitous I sent to the wrong e-mail, Yasuhiko already found the issue in
kde3 from a post to the opensuse list yesterday:
<quote>
This problem is that while referencing icon's file names, only reads up
to the first period (this is due to a default implementation of
QFileInfo::baseName()).
So that there is an issue where the selected icon is not reflected.
This problem occurs not only in Tumbleweed, but also in other versions.
Fix was already submitted to KDE:KDE3.
Binaries will be available soon.
</quote>
So if TDE has the same issue, you can grab the QFileInfo::baseName() patch
from there.
Keep up the great work!
--
David C. Rankin, J.D.,P.E.
Hey there,
I am working on changing the default TDE configuration for a Live ISO. I have read through the:
https://wiki.trinitydesktop.org/Customization_for_distributions
However, when I place my configuration files into /opt/trinity/share/config as well as trying with my own dir added to the TDEDIRS variable. I cannot get the default settings to apply. I can only get the new default settings to apply on the creation of a new account using /etc/skel.
Is there a new spot for the default TDE configs? Or am I just not looking in the right spots? Ideally when a user selects default at the bottom of a settings dialog (for the bottom panel for example), it uses the defaults I have set.
TDE devs,
Here is an odd bit of behavior with a new KDE3 install on openSUSE
Tumbleweed I'm trying to chase down and wonder if this has been seen on TDE
yet. The basic problem is with focus-follows-mouse set and no longer being
able to scroll Firefox or Thunderbird windows with the mouse-wheel UNLESS the
window is click and made top-level. (kinda defeats the purpose of
focus-follows-mouse...)
There is no question that the window receives focus, everything else works,
titlebar indicates focus, you can 'tab' between widgets in FF or TB, but the
mouse scroll does not work.
As a work-around you can set the environment variable
GDK_CORE_DEVICE_EVENTS=1 when starting either and then the focus-follows-mouse
works normally.
I've opened a bug:
Firefox Bug - no middle-mouse scroll on focused window not raised to top
https://bugzilla.mozilla.org/show_bug.cgi?id=1907708
only to find this is not a new issue:
Scrolling inactive windows in KDE/KWin with mouse wheel
https://bbs.archlinux.org/viewtopic.php?id=239918
Mousewheel action over Firefox doesn't work if Firefox window is not active
https://bugzilla.mozilla.org/show_bug.cgi?id=1359226
and to find this is likely related to the new KDE3 builds at openSUSE. I
have a Leap-15.4 install where KDE3 hasn't been updated since Sept. 2023 (it
was perfect -- why tempt something like this ....) So it may be related to
library version changes in the past 6 months or kernel differences between 5.4
and 6.9 or it could be due to a cockup in the build system.
Long story short I'm looking for more data points to help narrow down
where/what is causing this. Since this may be a Linux 6.9 or recent library
issue, I thought I would check if TDE has seen anything like this?
Also, a possible related issue has to do with the Run Command dialog
(Alt+F2) which I can summarize in a test case:
Test Case:
1. Alt + F2
2. type kmenuedit (tmenuedit on TDE IIRC)
3. return (to run it)
4. close kmenuedit
5. Alt + F2
6. type kmenuedit again
As you type the 'k' ('t' on TDE?) you will see the icon displayed change to
the kmenuedit icon showing at least the search-as-you-type part has identified
the prior kmenuedit command -- but -- the list-box does not open. You have to
manually click the list-box to see the previous kmenuedit command.
I don't know if this is related, but I thought I would add that scenario as
well. If you can't currently reproduce any of this -- good! But keep this in
mind if it should crop up in the future.
--
David C. Rankin, J.D.,P.E.
--
David C. Rankin, J.D.,P.E.
I thought I would get started with TDE programming, so I'm following the
steps in the Wiki Development section, "Qt Designer and KDevelop 3.0 for
Beginners". I followed the steps for creating the HelloWorld program
substituting TDevelop for KDevelop, and all went well until the Project Build
step, which failed, producing this output:
| cd '/home/development/TDEupdAlt/debug' && WANT_AUTOCONF_2_5="1"
WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" gmake -k
| gmake all-recursive
| gmake[1]: Entering directory '/home/development/TDEupdAlt/debug'
| Making all in doc
| gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/doc'
| Making all in .
| gmake[3]: Entering directory '/home/development/TDEupdAlt/debug/doc'
| gmake[3]: Nothing to be done for 'all-am'.
| gmake[3]: Leaving directory '/home/development/TDEupdAlt/debug/doc'
| Making all in en
| gmake[3]: Entering directory '/home/development/TDEupdAlt/debug/doc/en'
| /opt/trinity/bin/meinproc --check --cache
index.cache.bz2 /home/development/TDEupdAlt/doc/en/index.docbook
| gmake[3]: Leaving directory '/home/development/TDEupdAlt/debug/doc/en'
| gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/doc'
| Making all in po
| gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/po'
| gmake[2]: Nothing to be done for 'all'.
| gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/po'
| Making all in src
| gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/src'
|
g++ -DHAVE_CONFIG_H -I. -I/home/development/TDEupdAlt/src -I.. -I/opt/trinity/include/tde -I/usr/include/tqt3 -I. -include
tqt.h -DTQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT
main.o -MD -MP -MF .deps/main.Tpo -c -o
main.o /home/development/TDEupdAlt/src/main.cpp
| mv -f .deps/main.Tpo .deps/main.Po
| /usr/bin/tmoc /home/development/TDEupdAlt/src/tdeupdalt.h -o tdeupdalt.moc
|
g++ -DHAVE_CONFIG_H -I. -I/home/development/TDEupdAlt/src -I.. -I/opt/trinity/include/tde -I/usr/include/tqt3 -I. -include
tqt.h -DTQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT
tdeupdalt.o -MD -MP -MF .deps/tdeupdalt.Tpo -c -o
tdeupdalt.o /home/development/TDEupdAlt/src/tdeupdalt.cpp
| mv -f .deps/tdeupdalt.Tpo .deps/tdeupdalt.Po
| /bin/sh ../libtool --tag=CXX --mode=link
g++ -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -R /opt/trinity/lib64 -R /opt/trinity/lib64 -R /usr/lib64 -R /usr/lib64 -L/opt/trinity/lib64 -L/usr/lib64 -ltqt-mt -lz -lpng -lz -lm -lXext -lX11 -lSM -lICE -ltqt -lpthread -ltdecore -ltdeui -ltdeparts -o
tdeupdalt main.o tdeupdalt.o -ltdeui
| ../libtool: line 1300: func_opt_split: command not found
| libtool: Version mismatch error. This is libtool 2.2.6b
Debian-2.2.6b-2ubuntu1, but the
| libtool: definition of this LT_INIT comes from libtool 2.4.6.
| libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
Debian-2.2.6b-2ubuntu1
| libtool: and run autoconf again.
| gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/src'
| gmake[2]: *** [Makefile:629: tdeupdalt] Error 63
| gmake[2]: Target 'all' not remade because of errors.
| gmake[2]: Entering directory '/home/development/TDEupdAlt/debug'
| gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug'
| gmake[1]: Leaving directory '/home/development/TDEupdAlt/debug'
| gmake[1]: *** [Makefile:582: all-recursive] Error 1
| gmake: *** [Makefile:500: all] Error 2
| *** Exited with status: 2 ***
All went well until libtool was invoked, and I have to suppose that TDevelop
is (or thinks it is) using embedded libraries? because 1) I'm running on
openSUSE, not Debian ubuntu, and 2) my current installed libtool is
|@17:51:37 root@pinto
| wd=~
| ● rpm -q libtool
| libtool-2.4.6-150000.3.6.2.x86_64
| rc=0
Am I going to have to download TDevelop and compile it on my system?
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.5 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.2
tde-config: 1.0