Hi All,
When selecting not to use any login splash there is nonetheless some
kind of mini startup dialog. The dialog does not appear when using a
splash or possibly is hidden by the splash. Is there a way to disable
this mini startup dialog? None should mean none.
Thanks for your time!
DA
Hi,
is someone using pinentry-tqt?
Is it somehow in the list of available applications?
I was cleaning up and saw the conversion work that now I removed, because
the work was passed to GnuPG.
As I compile TDE myself and do not actually know what is available in the
package managers, I'm asking here.
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Every PC I try to remove avahi from wants to disgorge most of TDE, even though all
of them are running systemd-network with static configuration for eth0 and have no
wireless hardware, just like my KDE3 installations that don't require avahi. What
wouldn't work if avahi wasn't installed with TDE? Why does TDE require it?
--
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
The following is an extreme example, very old hardware, one PC, tried with two old
NVidia GPUs.
# lspci -nnk | grep -A2 VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (rev a1)
Subsystem: Palit Microsystems Inc. NV11 [GeForce2 MX/MX 400] [1569:0110]
Kernel driver in use: nouveau
# lspci -nnk | grep -A2 VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1)
Kernel driver in use: nouveau
Kernel modules: nouveau
# dpkg-query -l tdm-trinity
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-===========================-============-=================================
ii tdm-trinity 4:14.0.13-0debian12.0.0+0~a i386 X display manager for TDE
https://paste.debian.net/hidden/1d9bf7ac/ Xorg.0.log from failed first start
https://paste.debian.net/hidden/f1a49e73/ log from successful subsequent start
# systemd-analyze
Startup finished in 28.020s (kernel) + 2min 53.529s (userspace) = 3min 21.549s
graphical.target reached after 2min 53.482s in userspace.
From Xorg.0.logs, it looks like the server works fine, just takes longer than TDM's
default timeout. NAICT, the 120s default timeout isn't really all that long for some
hardware, but it appears TDM may not always try a second time, even though default
tries is 4.
https://bugzilla.opensuse.org/show_bug.cgi?id=1188954 may be related. It's much more
easily reproducible with TDM than with other DMs, and on openSUSE than elsewhere. Age
of hardware or drivers used don't seem to impact whether or not this happens. On an
given PC, it can't be counted on to happen every time. On the current one, after a
switch back to the newer of the two GPUs, it booted normally, though quite slowly.
I've seen this mostly on openSUSE, but today's is obviously from (32bit) Bookworm.
Have others encountered $SUBJECT? What's necessary to determine whether fault is
in TDM or elsewhere?
--
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
Dear developers and users,
after the release of TDE R14.0.13, we shared our tentative plan for
launching TDE R14.1.0 at the next release cycle. Since the development of
the last few tasks for R14.1.0 has been proceeding favorably, we now
consider the R14.0.x series to be closed and the next stable version to be
R14.1.0.
The deb packages repository known as PSB (Preliminary Stable Builds)
contains preliminary packages of the "upcoming stable version". Therefore,
this repository will be updated and will provide packages for R14.1.0~pre
in future. We intend to do this major update at the end of February. This
means that from that moment to the final release of R14.1.0, PSB and PTB
repositories will provide the same packages.
If you are using PSB repository, but do not want to participate in the
final phase of testing the upcoming R14.1.0, you should change your apt
sources and direct them to the final versions of R14.0.x series.
R14.1.0~pre is very stable, so the development team would appreciate if you
could help testing R14.1.0 before the final release.
Thank you for your participation in the development.
Slávek Banko
Hi All,
Is there a guideline to configure TDE to coexist fluidly with multiple
DEs installed? Beyond installing to /opt/. Tips and tricks. I searched
the wiki.
I would not mind discovering that after being away from TDE for some
years that I am not configuring or compiling correctly, but seems TDE is
somewhat designed with a presumption of only using TDE. Or possibly the
build scripts I found are configured incorrectly. One way or another I
need to know how environments should be configured inside and outside of
TDE.
* Correctly configure TDE and other DE or system environment variables.
* How to use TDE software when using a different DE.
* How to use KDE software when using TDE.
* How to not lose themes when using KDE software within TDE.
* Ensuring dbus/dcop are accessed correctly.
For example, when launching TDE the starttde script ensures $TDEDIR/bin
is in the environment $PATH just before /usr/bin. The opposite of that
is using TDE software in a different DE then $TDEDIR/bin needs to be in
$PATH just after /usr/bin (unless wanting to always type full paths).
Yet I am not aware of anything that automatically configures $PATH that way.
There are many TDE files with the same file names as in KDE, but that
does not mean all KDE software should be ignored. Yet launching KDE
software from within TDE (for me) results in a loss of toolbar icon
themes with the icons defaulting to flat icons. I can remedy that by
using a script wrapper to launch KDE software with the script modifying
XDG_CURRENT_DESKTOP=TDE:KDE. The change in the environment variable only
affects that process but helps avoid the loss of the toolbar icon theme.
Oddly, running KDE software inside other DEs has no such theme issues,
which implies something is incorrectly configured in (my) TDE (possibly
environment variables). Setting XDG_CURRENT_DESKTOP=TDE:KDE in the
environment before TDE fully launches causes some weird problems and
xsession log spew.
While XDG_CURRENT_DESKTOP and XDG_SESSION_DESKTOP support were added to
TDM, seems the support was not added for launching TDE from the console
with startx.
Other oddities include how the TDE GTK2 and GTK3 theme engines affect
other DEs. Weird things happens when those two TDE packages are installed.
Thanks for your time!
D.A
# rpm -e libtiff5
error: Failed dependencies:
libtiff.so.5()(64bit) is needed by (installed) trinity-tdelibs-14.0.13-1.osstw.x86_64
# zypse libtiff
| libtiff6-32bit | package | 4.5.0-2.1 | x86_64 | OSS
i | libtiff5 | package | 4.4.0-5.1 | x86_64 | (System Packages)
i | libtiff6 | package | 4.5.0-2.1 | x86_64 | OSS
--
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 All,
What is the preferred method for proposing patches?
I have a modified starttde script to propose.
Many of the changes are cosmetic: updating comments to fit within 80
columns, nominal grammar tweaks, moving a few comments to a more
appropriate location, and converting backticks to parentheses.
Another wave of changes includes FIXME comments where the script seems
outdated or in need of change.
A third wave includes (drum roll!) some actual changes.
Thanks for your time!
D.A.
