Where in KControl or elsewhere does one go to make pointer and I-bar large enough
to notice? In peripherals is only (4) mouse cursor themes, where exist no controls
for any sizes. The pointer in TDM is about 4X as large as in TDE sessions, and
appropriate for my needs. Is there a separate package to provide pointer controls
that isn't required in a base installation?
--
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
For the record - and in case somebody falls into the same trap:
I found the culprit: live-coniig handles parts of the boot process when running from a live image. That program is a decade old and has a strange idea on autologon and Xorg. If "autologin" is not explictly disabled, Xorg is started early in the boot process, bypassing sysv. When sysv later starts tdm it thinks X is not running which results in some demons started again which results in utter chaos.
So to prevent this disable autologin:
LIVE_CONFIG_CMDLINE="live-config.noautologin live-config.debug"
Note: If tdm was configurd to autologon, it will still autologon when booted from the iso.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Howdy,
I've got an issue where the layout and mode of my displays resets to the default at every login. This is despite me setting up the monitors in the TDE Control Center, both locally as my user and globally as root, creating an X config using the NVIDIA X Server Settings, and having no such issue previously when I was still using KDE Plasma.
I'm using the latest NVIDIA proprietary drivers on EndeavourOS, with a 1920x1080@60hz display on DP-1 and a 3440x1440@144hz display on DP-2. The ultrawide 1440p display is on the right slightly above the smaller one, but Trinity and TDM both repeatedly place them in the opposite arrangement with the smaller monitor as the default, sitting on the top right corner of the larger one. Both displays default to 60hz at login.
I've also tried enabling "Automatically apply profile on startup" and creating a profile, but when trying to reload it, X spits out an error "xrandr: cannot find mode 3440x1440". I don't get any such error when logging on, only when trying to load it manually from control center, which makes me think it's not even trying. I have not tested using xrandr manually from the command line.
How do I get Trinity to remember my monitor layout correctly? Is this a known issue?
\-- [bonkmaykr.xyz][]
Proud webmaster of KangWorlds.
Sent from Proton Mail mobile
[bonkmaykr.xyz]: https://bonkmaykr.xyz
Hi folks.
I have a friend who recently struggled with his previous desktop environment
so I slid Trinity towards him, and he has been using it since.
There is a small problem though, and one I never noticed: There seems to be no
way to change the mouse sensitivity under the settings. I thought this was
crazy when he told me he couldn't find it, but alas, he wasn't blind. There
is no slider anywhere for adjusting the mouse sensitivity.
"Well, perhaps this was an accidental regression at some point", I thought, as
I loaded KDE3 on a VM. "There is no way there was no slider in this desktop
for something as simple as mouse sensitivity." As wild as I thought that
claim would be, there also wasn't a slider in KDE3, only an option to change
the polling rate on supported mice, which explained to me the historic reason
as to why.
My friend is setting the sensitivity through xinput right now, but perhaps it
is time to add a slider to change mouse sensitivity. Those with
highly-sensitive mice shall Trinity with no fear! And just to check, I tried
turning the Pointer Threshold down and Acceleration up to see if that is a
hacky way to change sensitivity. It is not.
Or perhaps we are both blind as bats and the option was already there, right
in front of us. Please let us know.
--
Wirlaburla
Dear all,
May be off topic. I am trying to understand why Debian (especially stable)
has the reputation as being more conservative than other distributions. If
I look at distrowatch (for example comparing to openSUSE and Fedora):
Kernel LibreOffice Release date
Bookworm 6.1.27 7.4.5 2023-06-10
Trixie 6.6.15 24.2.0 2023-06-11
Leap 15.5 5.14.21 7.4.3.2 2023-06-07
Tumbleweed 6.7.9 24.2.1 2024-03-17
Fedora 6.5.6 7.6.2 2023-11-07
I don't know much about the meaning of kernel versions, but I know that
major versions are often developed in parallel. Is 5.14.21 newer than
6.1.27? Judging alone from the kernel version numbers (and other
packages), it looks like Leap would be the most conservative while Debian
Testing (Trixie) almost as up-to-date (concerning newer Linux packages) as
Tumbleweed and ahead of Fedora (released later).
Thanks,
Gianluca
-----------------------------------------------------
Gianluca Interlandi, PhD gianluca(a)u.washington.edu
+1 (206) 685 4435
http://gianluca.today/
Department of Bioengineering
University of Washington, Seattle WA U.S.A.
-----------------------------------------------------
Hi,
Is there a way to remove the sleep, suspend, hybernate, sleep and combos from
the logout menu within Trinity?
So far I have been unable to find configuration options for this. Therefor I
used polkit to disable these options system wide. I used the following code
in a file I created for this purpose in:
/etc/polkit-1/localauthority/50-local.d
[Disable suspend (logind)]
Identity=unix-user:*
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.hibernate;org.freedesktop.login1.hibernate-multiple-sessions
ResultActive=no
ResultInactive=no
ResultAny=no
This would remove all the undesired options in the logout menu. However, after
I updated to Trinity 14.1.1, the logout menu has now added a freeze option.
Searching for that on the internet gives me just about all the possible
results related to hanging or crashed systems but not what I'm looking for.
So my question is:
a) does Trinity have a native way to remove these suspend/hybernate/freeze/aso
options?
if not, then
b) does anyone know what needs to be added to the above Action line to let
polkit do it for me?
I'm running Trinity on Devuan 4, so no systemd here.
Regards,
Rody
This is the followup of "dcopserver starting twize".
As I am just creating a new Devuan+TDE ISO I ran into this naging problem again. When booting from the ISO created with refractasnapshot /etc/init.d/tde starts tdeinit twize in parallel. This leads to dcopserver running twize - sometimes one for root and one for $USER, sometimes both for $USER. My workaround for now: "service stop tdm; killall dcopserver" restarts TDE once.
Now my question is: where is that racecondition hidden that makes /etc/init.d/tde to start tdeinit twice in parallel? Any idea?
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Is there a recommended strategy to deal with Qt5 software in TDE?
This is somewhat like dealing with GTK software.
On my systems, Qt5 programs look awful in TDE, mostly really tiny fonts
and ignoring themes. Qt5 tools look normal when I use KDE.
I am aware of qt5ct. That tool provides some sanity with Qt5 tools in
TDE, but usage needs to be limited to TDE. Otherwise qt5ct introduces
its own frustrations in KDE.
Thanks.
Hi all!
Does anybody know which part of TDE controls XF86RaiseVolume / XF86LowerVolume? I need to remap these 2 keys to XF86LaunchA / XF86LaunchB but TDE always answers with the OSD volume bar, even when I remap the beys with xmodmap ...
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
