What needs to be changed to cut the wait time down from 90 seconds to 5 seconds when reboot is ordered by a root login on a vtty shell, and TDM is just sitting there on vtty7 doing nothing with nobody logged in? Current is Fedora 35, but this happens at random on any distro that uses systemd. Nothing shows up in journal to indicate any tde/tdm/twin problems.
# tail -n22 tdm.log [FIXME] UNCLASSIFIED DEVICE name: ptp0 type: (null) subsystem: ptp driver: e1000e [Node Path: /dev/ptp0] [Syspath: /sys/devices/pci0000:00/0000:00:1f.6/ptp/ptp0] [8086:15b8] [FIXME] UNCLASSIFIED DEVICE name: wmi_bus-PNP0C14:00 type: (null) subsystem: wmi_bus driver: acpi-wmi [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: F6CB5C3C-9CAE-4EBD-B577-931EA32A2CC0 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/F6CB5C3C-9CAE-4EBD-B577-931EA32A2CC0] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wmi_bus-PNP0C14:01 type: (null) subsystem: wmi_bus driver: acpi-wmi [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 05901221-D566-11D1-B2F0-00A0C9062910 type: data subsystem: wmi driver: wmi-bmof [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/05901221-D566-11D1-B2F0-00A0C9062910] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 466747A0-70EC-11DE-8A39-0800200C9A66 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/466747A0-70EC-11DE-8A39-0800200C9A66] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 97845ED0-4E6D-11DE-8A39-0800200C9A66 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/97845ED0-4E6D-11DE-8A39-0800200C9A66] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: ABBC0F72-8EA1-11D1-00A0-C90629100000 type: event subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/ABBC0F72-8EA1-11D1-00A0-C90629100000] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup22 type: (null) subsystem: wakeup driver: i8042 kbd [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:01/wakeup/wakeup22] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: cmos_nvram0 type: (null) subsystem: nvmem driver: (null) [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/cmos_nvram0] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup24 type: (null) subsystem: wakeup driver: alarmtimer [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/rtc/rtc0/alarmtimer.0.auto/wakeup/wakeup24] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup23 type: (null) subsystem: wakeup driver: rtc_cmos [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/wakeup/wakeup23] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: mc type: (null) subsystem: edac driver: (null) [Node Path: (null)] [Syspath: /sys/devices/system/edac/mc] [(null):(null)] /etc/trinity/tdm/Xsetup: line 7: syntax error: unexpected end of file /usr/bin/iceauth: creating new authority file /tmp/0935833680/.ICEauthority [2022/06/08 01:53:37.174] TQThreadInstance::start: Setting thread storage to 0x55bbcd43d050
[2022/06/08 01:53:37.234] TQObject::activate_signal: Invoking cross-thread method from object 0x55bbcd3f4b90 (member 2 receiver 0x55bbcd43fc60) (1)
(II) AIGLX: Suspending AIGLX clients for VT switch [2022/06/08 01:55:45.951] twin: Fatal IO error: client killed (II) Server terminated successfully (0). Closing log file.
# cat /etc/trinity/tdm/Xsetup #!/usr/bin/sh # Xsetup - run as root before the login dialog appears
#xconsole -geometry 480x130-0-0 -notify -verbose -fn fixed -exitOnFail -file /dev/xconsole &
if [ -x /home/setup ] ; then /home/setup # I have no idea why Xsetup: line 7: unexpected end of file occurs.
On 2022/06/08 03:14 PM, Felix Miata wrote:
What needs to be changed to cut the wait time down from 90 seconds to 5 seconds when reboot is ordered by a root login on a vtty shell, and TDM is just sitting there on vtty7 doing nothing with nobody logged in? Current is Fedora 35, but this happens at random on any distro that uses systemd. Nothing shows up in journal to indicate any tde/tdm/twin problems.
# tail -n22 tdm.log [FIXME] UNCLASSIFIED DEVICE name: ptp0 type: (null) subsystem: ptp driver: e1000e [Node Path: /dev/ptp0] [Syspath: /sys/devices/pci0000:00/0000:00:1f.6/ptp/ptp0] [8086:15b8] [FIXME] UNCLASSIFIED DEVICE name: wmi_bus-PNP0C14:00 type: (null) subsystem: wmi_bus driver: acpi-wmi [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: F6CB5C3C-9CAE-4EBD-B577-931EA32A2CC0 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/F6CB5C3C-9CAE-4EBD-B577-931EA32A2CC0] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wmi_bus-PNP0C14:01 type: (null) subsystem: wmi_bus driver: acpi-wmi [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 05901221-D566-11D1-B2F0-00A0C9062910 type: data subsystem: wmi driver: wmi-bmof [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/05901221-D566-11D1-B2F0-00A0C9062910] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 466747A0-70EC-11DE-8A39-0800200C9A66 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/466747A0-70EC-11DE-8A39-0800200C9A66] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 97845ED0-4E6D-11DE-8A39-0800200C9A66 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/97845ED0-4E6D-11DE-8A39-0800200C9A66] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: ABBC0F72-8EA1-11D1-00A0-C90629100000 type: event subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/ABBC0F72-8EA1-11D1-00A0-C90629100000] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup22 type: (null) subsystem: wakeup driver: i8042 kbd [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:01/wakeup/wakeup22] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: cmos_nvram0 type: (null) subsystem: nvmem driver: (null) [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/cmos_nvram0] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup24 type: (null) subsystem: wakeup driver: alarmtimer [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/rtc/rtc0/alarmtimer.0.auto/wakeup/wakeup24] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup23 type: (null) subsystem: wakeup driver: rtc_cmos [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/wakeup/wakeup23] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: mc type: (null) subsystem: edac driver: (null) [Node Path: (null)] [Syspath: /sys/devices/system/edac/mc] [(null):(null)] /etc/trinity/tdm/Xsetup: line 7: syntax error: unexpected end of file /usr/bin/iceauth: creating new authority file /tmp/0935833680/.ICEauthority [2022/06/08 01:53:37.174] TQThreadInstance::start: Setting thread storage to 0x55bbcd43d050
[2022/06/08 01:53:37.234] TQObject::activate_signal: Invoking cross-thread method from object 0x55bbcd3f4b90 (member 2 receiver 0x55bbcd43fc60) (1)
(II) AIGLX: Suspending AIGLX clients for VT switch [2022/06/08 01:55:45.951] twin: Fatal IO error: client killed (II) Server terminated successfully (0). Closing log file.
# cat /etc/trinity/tdm/Xsetup #!/usr/bin/sh # Xsetup - run as root before the login dialog appears
#xconsole -geometry 480x130-0-0 -notify -verbose -fn fixed -exitOnFail -file /dev/xconsole &
if [ -x /home/setup ] ; then /home/setup # I have no idea why Xsetup: line 7: unexpected end of file occurs.
Hi Felix, the 90s delays is the default timeout in systemd when somethings does not start/stop correctly... super annoying. I usually edit the /etc/systemd/system.conf file and add these lines in:
DefaultTimeoutStartSec=5s DefaultTimeoutStopSec=5s
This reduces the wait to 5s, which should be more than enough for any normal executing process to do what it needs.
Cheers Michele
Felix Miata wrote:
/etc/trinity/tdm/Xsetup
you simply shouldn't put stuff around in global files that is not meant to be interpreted globally
the original content of the file is
>>START
#! /bin/sh # Xsetup - run as root before the login dialog appears
#xconsole -geometry 480x130-0-0 ..... <<<<<<<<END
So try with the original file and see if it works
Also why posting this in the devel list, when it is clearly a user problem?
deloptes composed on 2022-06-09 08:20 (UTC+0200):
Felix Miata wrote:
/etc/trinity/tdm/Xsetup
you simply shouldn't put stuff around in global files that is not meant to be interpreted globally
Because what's in Xsetup is to be run before anybody logs in, so *is* a system thing. Clearly that's global. Nobody's logged in.
the original content of the file is
>>>START
#! /bin/sh # Xsetup - run as root before the login dialog appears
#xconsole -geometry 480x130-0-0 ..... <<<<<<<<END
Are you trying to say that #xconsole line constitutes EOF? How does a comment line get to be an EOF when a command sequence follows???
So try with the original file and see if it works
Sure it works, but then the /home/setup content (which is an xrandr command) isn't applied to Xorg startup before the greeter paints, is not "run as root before the login dialog appears".
Also why posting this in the devel list, when it is clearly a user problem?
Because it looks like Xsetup handling is broken.
Felix Miata wrote:
#xconsole -geometry 480x130-0-0 ..... <<<<<<<<END
Are you trying to say that #xconsole line constitutes EOF? How does a comment line get to be an EOF when a command sequence follows???
the error comes from the setup script obviously
So try with the original file and see if it works
Sure it works, but then the /home/setup content (which is an xrandr command) isn't applied to Xorg startup before the greeter paints, is not "run as root before the login dialog appears".
Also why posting this in the devel list, when it is clearly a user problem?
Because it looks like Xsetup handling is broken
I understand. I do not know how Xsetup is handled. It might be TDE or X whatever.
regarding the xrandr I use it in the user session and it works fine. So for setting this up globally a script in /etc/profile.d/ would probably do the same, but needs to check if X is already setup.
interesting topic
Am Freitag, 24. Juni 2022 schrieb Stefan Krusche:
Am Mittwoch, 8. Juni 2022 schrieb Felix Miata:
if [ -x /home/setup ] ; then /home/setup
Maybe this is no valid shell syntax because there should be no words after the keyword "then", AFAICT.
No, it is possible to write code after "then", but that should be a command, I think.
HTH
On Fri June 24 2022 01:13:33 Stefan Krusche wrote:
Am Freitag, 24. Juni 2022 schrieb Stefan Krusche:
Am Mittwoch, 8. Juni 2022 schrieb Felix Miata:
if [ -x /home/setup ] ; then /home/setup
Maybe this is no valid shell syntax because there should be no words after the keyword "then", AFAICT.
No, it is possible to write code after "then", but that should be a command, I think.
It says if /home/setup exists and is executable then execute it.
Felix reported "Xsetup: line 7: unexpected end of file" because there was no "fi" to match the "if".
Also /home is not a good place for a random "setup" script.
--Mike
Anno domini 2022 Fri, 24 Jun 01:21:53 -0700 Mike Bird scripsit:
On Fri June 24 2022 01:13:33 Stefan Krusche wrote:
Am Freitag, 24. Juni 2022 schrieb Stefan Krusche:
Am Mittwoch, 8. Juni 2022 schrieb Felix Miata:
if [ -x /home/setup ] ; then /home/setup
Maybe this is no valid shell syntax because there should be no words after the keyword "then", AFAICT.
No, it is possible to write code after "then", but that should be a command, I think.
It says if /home/setup exists and is executable then execute it.
Felix reported "Xsetup: line 7: unexpected end of file" because there was no "fi" to match the "if".
should be:
if [ -x /home/setup ] ; then /home/setup; fi
Also /home is not a good place for a random "setup" script.
--Mike ____________________________________________________ tde-devels mailing list -- devels@trinitydesktop.org To unsubscribe send an email to devels-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydeskt...
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Mike Bird composed on 2022-06-24 01:21 (UTC-0700):
/home is not a good place for a random "setup" script.
It's conveniently there for any ordinary user, all of which are me, to change at will, on a multiboot system on which /home/ is common to all installations. It's actually called from a symlink somewhere in /etc/X11/, the exact location of which varies by distro. Where would you put such a file?
On Fri June 24 2022 05:32:18 Felix Miata wrote:
Mike Bird composed on 2022-06-24 01:21 (UTC-0700):
/home is not a good place for a random "setup" script.
It's conveniently there for any ordinary user, all of which are me, to change at will, on a multiboot system on which /home/ is common to all installations. It's actually called from a symlink somewhere in /etc/X11/, the exact location of which varies by distro. Where would you put such a file?
Hi Felix,
The official answer would probably be /usr/local/bin although personally I use /IMS-Tools for ancient historical reasons.
/home already has a well-defined use-case and down the line you may find having a random script there interferes with some tool you might want to use to monitor disk usage or clean temporary files or update profiles.
Of course you're the administrator of your systems and know them better than I do but I wouldn't recommend anyone to copy your placement without understanding the trade-offs.
--Mike
Mike Bird composed on 2022-06-24 11:31 (UTC-0700):
Felix Miata wrote:
Mike Bird composed on 2022-06-24 01:21 (UTC-0700):
/home is not a good place for a random "setup" script.
It's conveniently there for any ordinary user, all of which are me, to change at will, on a multiboot system on which /home/ is common to all installations. It's actually called from a symlink somewhere in /etc/X11/, the exact location of which varies by distro. Where would you put such a file?
The official answer would probably be /usr/local/bin although personally I use /IMS-Tools for ancient historical reasons.
/home already has a well-defined use-case and down the line you may find having a random script there interferes with some tool you might want to use to monitor disk usage or clean temporary files or update profiles.
Of course you're the administrator of your systems and know them better than I do but I wouldn't recommend anyone to copy your placement without understanding the trade-offs.
The issue here is /usr/local/bin is really for the admin, not ordinary users. Another issue here is keystroke count, because as likely as unlikely not in X currently, cd .. or less ../setup or nano ../setup rather than mount... + sudo... + sudo... since ordinary users normally don't have write permission on files in /usr/local/bin. This setup file is currently nearly 1,000 lines, of which only one normally does not begin with "#", and the only task is to choose which # to move to the line where # currently is absent. All of this is primarily because of X's insistence on not allowing the computer to compute either the actual physical, or an alternate ideal, DPI to employ based upon EDID, or EDID ± configured deviation.
https://bugs.freedesktop.org/show_bug.cgi?id=23705 xserver forces 96 DPI on randr-1.2-capable drivers, overriding correct autodetection
https://bugs.freedesktop.org/show_bug.cgi?id=41115 Please add option to avoid forcing of 96dpi
-
deloptes -
Dr. Nikolaus Klepp -
Felix Miata -
Michele Calgaro -
Mike Bird -
Stefan Krusche