Both the primary and the old primary are getting a lot of these. They
started a couple months back but have recently become a lot more frequent
and over the last approx six hours all attempts have failed.
rsync: getaddrinfo: archive.trinitydesktop.net 873: Temporary failure in name
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139)
[Receiver=3.2.7]
I've tried a few times to reproduce them with dig but previously have been
unsuccessful. Here is a successful reproduction of the failure using dig:
$ dig +trace -t any archive.trinitydesktop.org
; <<>> DiG 9.18.16-1~deb12u1-Debian <<>> +trace -t any
archive.trinitydesktop.org
;; global options: +cmd
. 513855 IN NS b.root-servers.net.
. 513855 IN NS c.root-servers.net.
. 513855 IN NS d.root-servers.net.
. 513855 IN NS g.root-servers.net.
. 513855 IN NS i.root-servers.net.
. 513855 IN NS a.root-servers.net.
. 513855 IN NS m.root-servers.net.
. 513855 IN NS e.root-servers.net.
. 513855 IN NS l.root-servers.net.
. 513855 IN NS k.root-servers.net.
. 513855 IN NS h.root-servers.net.
. 513855 IN NS f.root-servers.net.
. 513855 IN NS j.root-servers.net.
;; Received 851 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms
org. 172800 IN NS a0.org.afilias-nst.info.
org. 172800 IN NS a2.org.afilias-nst.info.
org. 172800 IN NS b0.org.afilias-nst.org.
org. 172800 IN NS b2.org.afilias-nst.org.
org. 172800 IN NS c0.org.afilias-nst.info.
org. 172800 IN NS d0.org.afilias-nst.org.
org. 86400 IN DS 26974 8 2
4FEDE294C53F438A158C41D39489CD78A86BEB0D8A0AEAFF14745C0D 16E1DE32
org. 86400 IN RRSIG DS 8 1 86400 20230719170000
20230706160000 11019 .
GFUV+ognT5Y46phU5xS8ja6oQIA0SNo+ezvusC1rZ1qRRXbiz/S7WPuY
OLoR4+dV+059Z9FrhaD3VChcOjAtQkJsBA9lmFdbERzZN3eXVtZdS4Qw
U85/0tmPnKD0eYGAfEwrSyNNS1TzjMws5R1GdMPmxH065XPp1eqp08M7
pJ7lextMkwOMkvSM3EeO4eZzEHA76+u4IPUfHXPp6IXVyZR7cT3R58TI /a4dZsC3kbzY9IgVKoRFPeMg0cIXxvCha2iS0Rt8UxjijE8DMQB0J93k
5r5gf5Yl/lBVrvvVn+GooKGXGRahbhGbK2LllCqEHZuMim2q8YZW0uju CWzzsw==
;; Received 792 bytes from 192.58.128.30#53(j.root-servers.net) in 20 ms
trinitydesktop.org. 3600 IN NS ns1.rptsys.com.
trinitydesktop.org. 3600 IN NS ns2.rptsys.com.
trinitydesktop.org. 3600 IN DS 61248 10 2
A7B8B96ED5B3E79975D8DE2E1F0AA4B3EB19E223652D3C6C9EEB1F08 0E6F7FAC
trinitydesktop.org. 3600 IN DS 61248 10 1
6DDEE2E3E08F63DAEFBA3727EBFB0FC3476C357E
trinitydesktop.org. 3600 IN RRSIG DS 8 2 3600 20230722152257
20230701142257 33825 org.
RPoO3+TxUoK0bvlgUnDtDtkIJCJjOMoqfA4chVAE9vs3DrZpQox5SXQP
36J9HbR7MoDSxoBS6WG23AfFrMmhT64xE50YY0rVOLXZN/TEh+xPpV/3
GgOD1PznKsMhVFaL9sRu+jfTIyH4T817hALy4P99kdpz0Hz2SYMsopH/ lmE=
;; Received 348 bytes from 199.19.56.1#53(a0.org.afilias-nst.info) in 188 ms
trinitydesktop.org. 86400 IN SOA ns1.rptsys.com.
kb9vqf.pearsoncomputing.net. 2023070600 28800 3600 2419200 86400
trinitydesktop.org. 86400 IN RRSIG SOA 10 2 86400 20230805123001
20230706123001 49352 trinitydesktop.org.
a87gcAbIhNo1JPKzOFqDo+hAMDttdkeXc+QdFTr86wVnq2wzq1JbyfNJ
2ahDh/Tmygp4QXC+dZXbTyLe3Z7fqJt1DXaXueUzzPrAoZ/fA9XFgwHp
y1BwsCSjjEVGjvW7NcSBIuBadQr9f8qbFjNjhK/sY1h7oBgxZM6Zt0iu
x97AifisDnXtmvEUAmQ0R0IT0U3lspZku/LC6QLh24Pg84xC6vfdM95k
4qVguJ8hoPZyaQsye61qnpA7d6/vOVgJTCv4Mhn/U+d13wa2ncWY/B96
3/I96KV0aLNx66rT8wtxi/gW7I8YvjNhnSsre15eKlQCTrkOGVTbEho6 M4Woaw==
18N2QUN8GCH4VJFNGPRBAU31VK9TR553.trinitydesktop.org. 86400 IN NSEC3 1 1 10
BAF7643358C59CBF 29I8Q2H7J5DPBTRAJEOFM20GOOEM1I5M A NS SOA MX TXT RRSIG
DNSKEY NSEC3PARAM
18N2QUN8GCH4VJFNGPRBAU31VK9TR553.trinitydesktop.org. 86400 IN RRSIG NSEC3 10 3
86400 20230805123001 20230706123001 49352 trinitydesktop.org.
Lfw2eDJQX8ewQxUYDB0zjkP8hb7QLuNGpUejyWBBIsaVJhK7Yx2Cpgcu
IvqFYoMuIuuI5LI352z4S5dOPEMcno31uvFYTgWgZZGWZ0T6ykPvMuB/
4YDknUZhI+Y3EoWY8vZnAnk36G65zBBzIilkcjCl3/G34kY1upxwxy7H
9rYtHZ+W3umv6gcvpNhs6lZbk14rIPbi2sCWnh9PzCgseFMlEXaw00tq
u1JaJ4lNZjIsEhryR2EdFjVf+LFNZeVUzUBjiv70zE6/qIrsZnBSgJ3D
HPJdWdqiLXxunWatNrJJ9wYFPcuO2Khdw1FJM6OeKM2jv4Twfd7RbttA Pjqy9w==
N7KV211739T3H6EVPS9DJRPIG177TULP.trinitydesktop.org. 86400 IN NSEC3 1 1 10
BAF7643358C59CBF P0SGO622HMGN0G8LCR8UPU8KI9GCAEC7 A RRSIG
N7KV211739T3H6EVPS9DJRPIG177TULP.trinitydesktop.org. 86400 IN RRSIG NSEC3 10 3
86400 20230805123001 20230706123001 49352 trinitydesktop.org.
oMQjHI6kI24lXbc2qBMInDbgmuqRIfRLZk5u3oq6D3sR1Xc7HLPGIoN+
kN2zLt1WoPMLGzVgOPl2/+LM/H1ODI5mdEajRkpy9Gol5JB3KsBRaec0
2xDvjzFsDnzq8wvMl6c4TwSwS38W3LyZpPsuQatrC1LmQ8Eemfma6hqO
XMJJzK/rGcumEwJCpfvDn2sHIl6dwHlpnAvySsrlZVFWC6TEq2vrG816
yhW/6Lb+0DvLp/e8pdbR4GVotewDoRyGMOt9cL31YXDvdIFxLnruPBlt
WTy7PzIqxoNHzCS6Vn+I74j3rvptO0sAael9nRQbsbV9dlSgSVDp1Wly rHVshg==
93KKHI1QT7IH1BFLF59NE9BQI6QO2CHL.trinitydesktop.org. 86400 IN NSEC3 1 1 10
BAF7643358C59CBF B4M0OS0M9S7V6LN09E5JC9471DUAV7IQ
93KKHI1QT7IH1BFLF59NE9BQI6QO2CHL.trinitydesktop.org. 86400 IN RRSIG NSEC3 10 3
86400 20230805123001 20230706123001 49352 trinitydesktop.org.
d1BP1ExNoJHp1ZA+izPMW7/Gya1eq5V58uIG/dl5d9e/AcwUtbJOULxz
vPEbGFzvmN0X4agafcifmsT5SEjlfi2ufk8EfHsgvwX0J+nJIYUrilve
qFQk2OihhWF3gfhcArV0qn8Iwp2xAQDEab4FddyAaQ8VW1IfAwnqgtT0
CyEs+t9uGl2IZJwVqDX8gq0I7mU+j9tot6c1pCYnD4yjrSEAhMWNLEjh
ZxLd6qJ8XedrxsLoD+x51aiDEW329BRh7nQcF8PXz+c7Z/Z3SFiQV/F4
XTVYC4W/iry2w/AyliwI2+H/0+ScUV7Z72BuTJBOxyz4AD5/uVfz2aaS cBlUGA==
;; Received 1638 bytes from 23.155.224.10#53(ns1.rptsys.com) in 80 ms
--Mike
Haldo! Long time user, first time poster!
It's weird looking back at all the different windows decorations and styles for KDE 3, knowing full well how much they not only had to be designed, but also coded. It's also weird knowing that some Trinity users haven't been exposed to some of these, however impractical or redundant they may be. xD
Me personally, I've been wanting to get the Fahrenheit windeco working in TDE (and not through lack of trying, mind you -- I really tried to figuring out porting, thank you to the wiki contributors, though I've not had much success. Possibly out of general inexperience with porting, makefiles, and development in general, but I digress....)
To be honest, I want to get the community's (or at least the devel list's) opinion on how feasible they think it is to get all the other Qt3 and KWin styles ported over to Trinity. I imagine the best starting point for this would be within openSUSE for a couple reasons:
- their interoperability with multiple distros and their respective package formats
- the fact that (as of this message) they still maintain a KDE3 repo, even in 2023 with Plasma 6 on its way
- some windecos don't have much documentation outside of guesswork and the obvious "made over a decade ago for a much different version" disclaimer (...hello again, Fahrenheit!)
Of course, my programming experience only extends beyond my use of Scratch as an elementary school young-un in the late-aughts, so I honestly don't know -- wdyt?
- hunter graham
Hi Michele, Slavek, all,
The recent changes QT_* -> TQT_* in headers (example Q_EXPORT -> TQ_EXPORT)
are impacting the pinentry application.
I remember we discussed once how we'll proceed with updates, but I do not
recall. I could prepare the patches and probably push upstream.
What is your view on this matter?
thanks in advance
BR
E.
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Recent KDE3s no longer require *arts*. Why does TDE? As if alsa shouldn't be
enough to start with on Linux, most newer installations have been moving from
pulseaudio to pipewire/plumber. What is it that arts offers? Doesn't its presence
get tangled with pulse/pipe?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Hi,
in packaging the metapackage for desktop-base somehow has more than the
debian directory.
Is it an error in the master repo or in my local copy and how to repair?
tde/1_git/tde/packaging/debian/_base/metapackages/desktop-base$ ls
backgrounds debian-desktop-logo.png debian-reference.desktop emblems
kompmgr-rc-files Makefile profiles splashy usplash
debian debian-homepage.desktop debian-security.desktop
gnome-backgrounds.xml ksplash-theme pixmaps splash tdm-theme
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Felix Miata composed on 2023-08-14 02:22 (UTC-0400):
> This has been going on too long to remember, probably more than a year now, but at
> least since 14.0.13. I haven't been able to create a reliable reproduction
> scenario. Typically, I start a session that has remembered Konsole (at 0,0) with a
> plain shell tab and an MC tab. With quite some frequency, I wish to copy and paste
> the first command of the session, and its output, that I have entered in the shell
> tab, into some text file in MC. The problem is that swiping the mouse from bottom
> to top to select that output commonly blanks the first Konsole line, which is
> usually something that produces multiple lines of text output, such as inxi, so
> that when pasted, the first line of the paste is also blank. The instant case
> causing me to write this is in Mageia 8/14.1.0, but it IIRC it happens in Debian,
> Fedora, openSUSE & *buntu also.
FTR, this definitely is happening in Trixie.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Attached tdm.log is from Fedora 39. In past several years through last spring,
I've had nominal trouble running the TDE for latest release on whatever release is
upcoming, in this case, F38>F39. This one on Kaby Lake host ab250 won't more than
pretend to start a TDE session either from startx or TDM. Attempting to start one
brings some screen flashing, then TDM returns. Selecting IceWM session instead of
TDE produces same result. I find no clues to session failure in journal, dmesg,
Xorg.X.log or .xsession-errors, while tdm.log grows from 0 to nearly 40k from just
starting, before any attempt to login.
An unlogged clue may be seen in session type selection: no matter what is selected
for current session (attempt), on the next return to session selection, "previous"
remains where it was before the upgrade from F38 to F39, on the second of the two
TDEs, right above failsafe.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
This has been an irritation for a long time, but various components of TDE
are crashing more and more frequently on my machine, and the Crash Handler is
never able to send its reports to you. I have attached what the Crash
Handler says whenever I try.
Has this method of reporting failures become obsolete? If so, why is the
code still there, misleading users who try to report failures?
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.4 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.0
tde-config: 1.0
I don't know enough about TDE development to know if you TDE developers need
to be aware of this but I thought I should post it here just in case.
https://lists.debian.org/debian-devel/2023/08/msg00311.html
Thanks for all you do!
--Mike
