Re: [fedora] fixme fixme fixme

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anno domini 2023 Thu, 21 Sep 06:04:10 -0400
 Felix Miata via tde-devels scripsit:
> Dr. Nikolaus Klepp composed on 2023-09-21 08:38 (UTC+0200):
>
> > 2023 Wed, 20 Sep 18:52:45 -0400 Felix Miata via tde-devels scripsit:
>
> >> 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.
>
> > Can you post what' in /etc/trinity/tdm/Xsetup?
> > [2023/09/20 18:30:28.215] tdelauncher: Fatal IO error: client killed
> > [2023/09/20 18:30:28.215] kded: Fatal IO error: client killed
> > /etc/trinity/tdm/Xsetup: line 7: syntax error: unexpected end of file
> > [2023/09/20 18:30:28.228] ---------------------------------
> > [dcopserver] It looks like dcopserver is already running. If you are sure
> > that it is not already running, remove /tmp/0472344363/.DCOPserver_ab250__0
> > and start dcopserver again.
>
>  # diff -u Xsetup /dev/null
> --- Xsetup      2022-02-18 01:21:18.000000000 -0500
> +++ /dev/null   2023-09-21 05:39:09.030708985 -0400
> @@ -1,6 +0,0 @@
> -#!/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
>
> My Xsetup was working fine 19 months. What changed to make it fail so spectacularly?
>
> Adding a line 7
>
> 	fi
>
> or appending
>
> 	; fi
>
> to line 6 doesn't help. Neither does restoring the original Xsetup from early 2022.

Can you post the file without diff?

Her on devuan it says (cat /etc/trinity/tdm/Xsetup):

#! /bin/sh
# Xsetup - run as root before the login dialog appears

#xconsole -geometry 480x130-0-0 -notify -verbose -fn fixed -exitOnFail -file /dev/xconsole &

... so it does nothing. Where does your /home/setup come from?

Nik




--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
____________________________________________________
tde-devels mailing list -- devels@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devels-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@xxxxxxxxxxxxxxxxxx



[Index of Archives]     [Trinity Users]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [KDE]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux