On Tue, 7 Feb 2023 22:27:14 -0800 (PST), hongy...@gmail.com wrote:
> On Wednesday, February 8, 2023 at 10:25:47 AM UTC+8, Bit Twister wrote:
>> On Mon, 6 Feb 2023 01:40:42 -0800 (PST), hongy...@gmail.com wrote:
>> > On Thursday, January 26, 2023 at 9:52:05 PM UTC+8, Bit Twister wrote:
>> >> On Wed, 25 Jan 2023 23:17:06 -0800 (PST), hongy...@gmail.com wrote:
>> >>
>> >> > Recently, I always meet the "Are you sure you want to proceed?" message on login as described here [1], and none of the above logs give me some clues. I want to disable the above message window to appear each time when I'm trying to log in and still failed to figure out the solution.
>> >> I suggest creating a test account, say junk. Log out of hongyi and into junk.
>> >> If junk has the same problem as hongyi you know it is a system wide problem.
>> >> If junk does not have the problem then you know it is a user (hongyi) problem.
>> >>
>> >> You can test the login process from either account by logging into the
>> >> other user account by clicking up a terminal and doing
>> >> su - junk
>> >> from a hongyi terminal or su - hongyi from a junk terminal, depending
>> >> on who you want to test.
>> >>
>> >> For you, I suggest anytime you make any login script change is to
>> >> su - junk and very there are no problems.
>> >
>> > According to the above suggestions, I conducted the following test:
>> >
>> > werner@X10DAi:~$ sudo useradd test
>> > werner@X10DAi:~$ sudo passwd test # Set the pw as: asdf1234
>> > werner@X10DAi:~$ sudo usermod -d /home/test -s /bin/bash test
>> > werner@X10DAi:~$ sudo mkdir /home/test
>> >
>> > # This time, the problem discussed here doesn't appear again:
>> > werner@X10DAi:~$ su - test
>> > Password:
>> > test@X10DAi:~$
>> >
>> > So, I tried to login back as follows and the problem appeared once more:
>> >
>> > test@X10DAi:~$ su - werner
>> > Password:
>> > terminate called after throwing an instance of 'std::runtime_error'
>> > what(): Failed to create dbus connection
>> > xhost: unable to open display ""
>> > dirname: invalid option -- 'b'
>> > Try 'dirname --help' for more information.
>> > readlink: invalid option -- 'b'
>> > Try 'readlink --help' for more information.
>> >su - werner
>> > Any tips for further debugging?
>> if su - test works and su - werner failed
>> then some script executed by werner login is failing.
>>
>> No idea why
>>
>> Message about dirname and readlink aught to be fixed.
>>
>> Apparently you are running some script executing those instructions that
>> test does not execute.
>>
>> By the way, after spending years as an maintenance programmer I found it beneficial
>> to fix any errors I find even if I believe they have no bearing on the problem
>> I am trying to fix.
>>
>> For your xhost problem I would need to see the xhost command. Looking through my
>> host xx__local.sh script I have
>> # grep xhost xx__local.sh
>> /local/bin/set_xhost +"$(hostname --fqdn)"
>> /local/bin/set_xhost +localhost >
>> xhost +local:docker
>>
>> You may want to consider install/using shellcheck to check your scripts.
>
> I wonder whether there is a similar but targeting for generating detail debug messages of startup scripts (profile, .bashrc, etc...).

For debugging a script I use
script -c "bash -x script_to_debug_here" a.log

As for login scripts which I need to see when something changed modified
/etc/profile to check if $HOME/debug is executable and if so run it.
Test is before/after each login script. Example snippet from /etc/profile
follows"

for i in /etc/profile.d/*.sh /etc/profile.d/sh.local ; do
if [ -r "$i" ]; then
if [ "${-#*i}" != "$-" ]; then
if [ -x $HOME/debug ] ; then
. $HOME/debug "starting $i "
fi
. "$i"
if [ -x $HOME/debug ] ; then
. $HOME/debug "finished $i "
fi
else
if [ -x $HOME/debug ] ; then
. $HOME/debug "starting $i "
fi
. "$i" >/dev/null
if [ -x $HOME/debug ] ; then
. $HOME/debug "finished $i "
fi
fi
fi
done

On Friday, February 17, 2023 at 8:00:53 PM UTC+8, Bit Twister wrote:
> On Tue, 7 Feb 2023 22:27:14 -0800 (PST), hongy...@gmail.com wrote:
> > On Wednesday, February 8, 2023 at 10:25:47 AM UTC+8, Bit Twister wrote:
> >> On Mon, 6 Feb 2023 01:40:42 -0800 (PST), hongy...@gmail.com wrote:
> >> > On Thursday, January 26, 2023 at 9:52:05 PM UTC+8, Bit Twister wrote:
> >> >> On Wed, 25 Jan 2023 23:17:06 -0800 (PST), hongy...@gmail.com wrote:
> >> >>
> >> >> > Recently, I always meet the "Are you sure you want to proceed?" message on login as described here [1], and none of the above logs give me some clues. I want to disable the above message window to appear each time when I'm trying to log in and still failed to figure out the solution.
> >> >> I suggest creating a test account, say junk. Log out of hongyi and into junk.
> >> >> If junk has the same problem as hongyi you know it is a system wide problem.
> >> >> If junk does not have the problem then you know it is a user (hongyi) problem.
> >> >>
> >> >> You can test the login process from either account by logging into the
> >> >> other user account by clicking up a terminal and doing
> >> >> su - junk
> >> >> from a hongyi terminal or su - hongyi from a junk terminal, depending
> >> >> on who you want to test.
> >> >>
> >> >> For you, I suggest anytime you make any login script change is to
> >> >> su - junk and very there are no problems.
> >> >
> >> > According to the above suggestions, I conducted the following test:
> >> >
> >> > werner@X10DAi:~$ sudo useradd test
> >> > werner@X10DAi:~$ sudo passwd test # Set the pw as: asdf1234
> >> > werner@X10DAi:~$ sudo usermod -d /home/test -s /bin/bash test
> >> > werner@X10DAi:~$ sudo mkdir /home/test
> >> >
> >> > # This time, the problem discussed here doesn't appear again:
> >> > werner@X10DAi:~$ su - test
> >> > Password:
> >> > test@X10DAi:~$
> >> >
> >> > So, I tried to login back as follows and the problem appeared once more:
> >> >
> >> > test@X10DAi:~$ su - werner
> >> > Password:
> >> > terminate called after throwing an instance of 'std::runtime_error'
> >> > what(): Failed to create dbus connection
> >> > xhost: unable to open display ""
> >> > dirname: invalid option -- 'b'
> >> > Try 'dirname --help' for more information.
> >> > readlink: invalid option -- 'b'
> >> > Try 'readlink --help' for more information.
> >> >su - werner
> >> > Any tips for further debugging?
> >> if su - test works and su - werner failed
> >> then some script executed by werner login is failing.
> >>
> >> No idea why
> >>
> >> Message about dirname and readlink aught to be fixed.
> >>
> >> Apparently you are running some script executing those instructions that
> >> test does not execute.
> >>
> >> By the way, after spending years as an maintenance programmer I found it beneficial
> >> to fix any errors I find even if I believe they have no bearing on the problem
> >> I am trying to fix.
> >>
> >> For your xhost problem I would need to see the xhost command. Looking through my
> >> host xx__local.sh script I have
> >> # grep xhost xx__local.sh
> >> /local/bin/set_xhost +"$(hostname --fqdn)"
> >> /local/bin/set_xhost +localhost >
> >> xhost +local:docker
> >>
> >> You may want to consider install/using shellcheck to check your scripts.
> >
> > I wonder whether there is a similar but targeting for generating detail debug messages of startup scripts (profile, .bashrc, etc...).
> For debugging a script I use
> script -c "bash -x script_to_debug_here" a.log
>
> As for login scripts which I need to see when something changed modified
> /etc/profile to check if $HOME/debug is executable and if so run it.
> Test is before/after each login script. Example snippet from /etc/profile
> follows"
>
>
> for i in /etc/profile.d/*.sh /etc/profile.d/sh.local ; do
> if [ -r "$i" ]; then
> if [ "${-#*i}" != "$-" ]; then
> if [ -x $HOME/debug ] ; then
> . $HOME/debug "starting $i "
> fi
> . "$i"
> if [ -x $HOME/debug ] ; then
> . $HOME/debug "finished $i "
> fi
> else
> if [ -x $HOME/debug ] ; then
> . $HOME/debug "starting $i "
> fi
> . "$i" >/dev/null
> if [ -x $HOME/debug ] ; then
> . $HOME/debug "finished $i "
> fi
> fi
> fi
> done

Nice idea. Thank you very much again. I will try to follow your prompts for further inspection and testing.

Regards,
Zhao

On Saturday, February 25, 2023 at 9:41:06 AM UTC-6, hongy...@gmail.com wrote:
> On Friday, February 17, 2023 at 8:00:53 PM UTC+8, Bit Twister wrote:
> > On Tue, 7 Feb 2023 22:27:14 -0800 (PST), hongy...@gmail.com wrote:
> > > On Wednesday, February 8, 2023 at 10:25:47 AM UTC+8, Bit Twister wrote:
> > >> On Mon, 6 Feb 2023 01:40:42 -0800 (PST), hongy...@gmail.com wrote:
> > >> > On Thursday, January 26, 2023 at 9:52:05 PM UTC+8, Bit Twister wrote:
> > >> >> On Wed, 25 Jan 2023 23:17:06 -0800 (PST), hongy...@gmail.com wrote:
> > >> >>
> > >> >> > Recently, I always meet the "Are you sure you want to proceed?" message on login as described here [1], and none of the above logs give me some clues. I want to disable the above message window to appear each time when I'm trying to log in and still failed to figure out the solution.
> > >> >> I suggest creating a test account, say junk. Log out of hongyi and into junk.
> > >> >> If junk has the same problem as hongyi you know it is a system wide problem.
> > >> >> If junk does not have the problem then you know it is a user (hongyi) problem.
> > >> >>
> > >> >> You can test the login process from either account by logging into the
> > >> >> other user account by clicking up a terminal and doing
> > >> >> su - junk
> > >> >> from a hongyi terminal or su - hongyi from a junk terminal, depending
> > >> >> on who you want to test.
> > >> >>
> > >> >> For you, I suggest anytime you make any login script change is to
> > >> >> su - junk and very there are no problems.
> > >> >
> > >> > According to the above suggestions, I conducted the following test:
> > >> >
> > >> > werner@X10DAi:~$ sudo useradd test
> > >> > werner@X10DAi:~$ sudo passwd test # Set the pw as: asdf1234
> > >> > werner@X10DAi:~$ sudo usermod -d /home/test -s /bin/bash test
> > >> > werner@X10DAi:~$ sudo mkdir /home/test
> > >> >
> > >> > # This time, the problem discussed here doesn't appear again:
> > >> > werner@X10DAi:~$ su - test
> > >> > Password:
> > >> > test@X10DAi:~$
> > >> >
> > >> > So, I tried to login back as follows and the problem appeared once more:
> > >> >
> > >> > test@X10DAi:~$ su - werner
> > >> > Password:
> > >> > terminate called after throwing an instance of 'std::runtime_error'
> > >> > what(): Failed to create dbus connection
> > >> > xhost: unable to open display ""
> > >> > dirname: invalid option -- 'b'
> > >> > Try 'dirname --help' for more information.
> > >> > readlink: invalid option -- 'b'
> > >> > Try 'readlink --help' for more information.
> > >> >su - werner
> > >> > Any tips for further debugging?
> > >> if su - test works and su - werner failed
> > >> then some script executed by werner login is failing.
> > >>
> > >> No idea why
> > >>
> > >> Message about dirname and readlink aught to be fixed.
> > >>
> > >> Apparently you are running some script executing those instructions that
> > >> test does not execute.
> > >>
> > >> By the way, after spending years as an maintenance programmer I found it beneficial
> > >> to fix any errors I find even if I believe they have no bearing on the problem
> > >> I am trying to fix.
> > >>
> > >> For your xhost problem I would need to see the xhost command. Looking through my
> > >> host xx__local.sh script I have
> > >> # grep xhost xx__local.sh
> > >> /local/bin/set_xhost +"$(hostname --fqdn)"
> > >> /local/bin/set_xhost +localhost >
> > >> xhost +local:docker
> > >>
> > >> You may want to consider install/using shellcheck to check your scripts.
> > >
> > > I wonder whether there is a similar but targeting for generating detail debug messages of startup scripts (profile, .bashrc, etc...).
> > For debugging a script I use
> > script -c "bash -x script_to_debug_here" a.log
> >
> > As for login scripts which I need to see when something changed modified
> > /etc/profile to check if $HOME/debug is executable and if so run it.
> > Test is before/after each login script. Example snippet from /etc/profile
> > follows"
> >
> >
> > for i in /etc/profile.d/*.sh /etc/profile.d/sh.local ; do
> > if [ -r "$i" ]; then
> > if [ "${-#*i}" != "$-" ]; then
> > if [ -x $HOME/debug ] ; then
> > . $HOME/debug "starting $i "
> > fi
> > . "$i"
> > if [ -x $HOME/debug ] ; then
> > . $HOME/debug "finished $i "
> > fi
> > else
> > if [ -x $HOME/debug ] ; then
> > . $HOME/debug "starting $i "
> > fi
> > . "$i" >/dev/null
> > if [ -x $HOME/debug ] ; then
> > . $HOME/debug "finished $i "
> > fi
> > fi
> > fi
> > done
> Nice idea. Thank you very much again. I will try to follow your prompts for further inspection and testing.
>
> Regards,
> Zhao
feeeeresrsdrdcv

On Tuesday, March 7, 2023 at 2:53:40 PM UTC-6, Jalen Q wrote:
> On Saturday, February 25, 2023 at 9:41:06 AM UTC-6, hongy...@gmail.com wrote:
> > On Friday, February 17, 2023 at 8:00:53 PM UTC+8, Bit Twister wrote:
> > > On Tue, 7 Feb 2023 22:27:14 -0800 (PST), hongy...@gmail.com wrote:
> > > > On Wednesday, February 8, 2023 at 10:25:47 AM UTC+8, Bit Twister wrote:
> > > >> On Mon, 6 Feb 2023 01:40:42 -0800 (PST), hongy...@gmail.com wrote:
> > > >> > On Thursday, January 26, 2023 at 9:52:05 PM UTC+8, Bit Twister wrote:
> > > >> >> On Wed, 25 Jan 2023 23:17:06 -0800 (PST), hongy...@gmail.com wrote:
> > > >> >>
> > > >> >> > Recently, I always meet the "Are you sure you want to proceed?" message on login as described here [1], and none of the above logs give me some clues. I want to disable the above message window to appear each time when I'm trying to log in and still failed to figure out the solution.
> > > >> >> I suggest creating a test account, say junk. Log out of hongyi and into junk.
> > > >> >> If junk has the same problem as hongyi you know it is a system wide problem.
> > > >> >> If junk does not have the problem then you know it is a user (hongyi) problem.
> > > >> >>
> > > >> >> You can test the login process from either account by logging into the
> > > >> >> other user account by clicking up a terminal and doing
> > > >> >> su - junk
> > > >> >> from a hongyi terminal or su - hongyi from a junk terminal, depending
> > > >> >> on who you want to test.
> > > >> >>
> > > >> >> For you, I suggest anytime you make any login script change is to
> > > >> >> su - junk and very there are no problems.
> > > >> >
> > > >> > According to the above suggestions, I conducted the following test:
> > > >> >
> > > >> > werner@X10DAi:~$ sudo useradd test
> > > >> > werner@X10DAi:~$ sudo passwd test # Set the pw as: asdf1234
> > > >> > werner@X10DAi:~$ sudo usermod -d /home/test -s /bin/bash test
> > > >> > werner@X10DAi:~$ sudo mkdir /home/test
> > > >> >
> > > >> > # This time, the problem discussed here doesn't appear again:
> > > >> > werner@X10DAi:~$ su - test
> > > >> > Password:
> > > >> > test@X10DAi:~$
> > > >> >
> > > >> > So, I tried to login back as follows and the problem appeared once more:
> > > >> >
> > > >> > test@X10DAi:~$ su - werner
> > > >> > Password:
> > > >> > terminate called after throwing an instance of 'std::runtime_error'
> > > >> > what(): Failed to create dbus connection
> > > >> > xhost: unable to open display ""
> > > >> > dirname: invalid option -- 'b'
> > > >> > Try 'dirname --help' for more information.
> > > >> > readlink: invalid option -- 'b'
> > > >> > Try 'readlink --help' for more information.
> > > >> >su - werner
> > > >> > Any tips for further debugging?
> > > >> if su - test works and su - werner failed
> > > >> then some script executed by werner login is failing.
> > > >>
> > > >> No idea why
> > > >>
> > > >> Message about dirname and readlink aught to be fixed.
> > > >>
> > > >> Apparently you are running some script executing those instructions that
> > > >> test does not execute.
> > > >>
> > > >> By the way, after spending years as an maintenance programmer I found it beneficial
> > > >> to fix any errors I find even if I believe they have no bearing on the problem
> > > >> I am trying to fix.
> > > >>
> > > >> For your xhost problem I would need to see the xhost command. Looking through my
> > > >> host xx__local.sh script I have
> > > >> # grep xhost xx__local.sh
> > > >> /local/bin/set_xhost +"$(hostname --fqdn)"
> > > >> /local/bin/set_xhost +localhost >
> > > >> xhost +local:docker
> > > >>
> > > >> You may want to consider install/using shellcheck to check your scripts.
> > > >
> > > > I wonder whether there is a similar but targeting for generating detail debug messages of startup scripts (profile, .bashrc, etc...).
> > > For debugging a script I use
> > > script -c "bash -x script_to_debug_here" a.log
> > >
> > > As for login scripts which I need to see when something changed modified
> > > /etc/profile to check if $HOME/debug is executable and if so run it.
> > > Test is before/after each login script. Example snippet from /etc/profile
> > > follows"
> > >
> > >
> > > for i in /etc/profile.d/*.sh /etc/profile.d/sh.local ; do
> > > if [ -r "$i" ]; then
> > > if [ "${-#*i}" != "$-" ]; then
> > > if [ -x $HOME/debug ] ; then
> > > . $HOME/debug "starting $i "
> > > fi
> > > . "$i"
> > > if [ -x $HOME/debug ] ; then
> > > . $HOME/debug "finished $i "
> > > fi
> > > else
> > > if [ -x $HOME/debug ] ; then
> > > . $HOME/debug "starting $i "
> > > fi
> > > . "$i" >/dev/null
> > > if [ -x $HOME/debug ] ; then
> > > . $HOME/debug "finished $i "
> > > fi
> > > fi
> > > fi
> > > done
> > Nice idea. Thank you very much again. I will try to follow your prompts for further inspection and testing.
> >
> > Regards,
> > Zhao
> feeeeresrsdrdcv
cddffdfdfd

On Tuesday, March 7, 2023 at 2:53:40 PM UTC-6, Jalen Q wrote:
> On Saturday, February 25, 2023 at 9:41:06 AM UTC-6, hongy...@gmail.com wrote:
> > On Friday, February 17, 2023 at 8:00:53 PM UTC+8, Bit Twister wrote:
> > > On Tue, 7 Feb 2023 22:27:14 -0800 (PST), hongy...@gmail.com wrote:
> > > > On Wednesday, February 8, 2023 at 10:25:47 AM UTC+8, Bit Twister wrote:
> > > >> On Mon, 6 Feb 2023 01:40:42 -0800 (PST), hongy...@gmail.com wrote:
> > > >> > On Thursday, January 26, 2023 at 9:52:05 PM UTC+8, Bit Twister wrote:
> > > >> >> On Wed, 25 Jan 2023 23:17:06 -0800 (PST), hongy...@gmail.com wrote:
> > > >> >>
> > > >> >> > Recently, I always meet the "Are you sure you want to proceed?" message on login as described here [1], and none of the above logs give me some clues. I want to disable the above message window to appear each time when I'm trying to log in and still failed to figure out the solution.
> > > >> >> I suggest creating a test account, say junk. Log out of hongyi and into junk.
> > > >> >> If junk has the same problem as hongyi you know it is a system wide problem.
> > > >> >> If junk does not have the problem then you know it is a user (hongyi) problem.
> > > >> >>
> > > >> >> You can test the login process from either account by logging into the
> > > >> >> other user account by clicking up a terminal and doing
> > > >> >> su - junk
> > > >> >> from a hongyi terminal or su - hongyi from a junk terminal, depending
> > > >> >> on who you want to test.
> > > >> >>
> > > >> >> For you, I suggest anytime you make any login script change is to
> > > >> >> su - junk and very there are no problems.
> > > >> >
> > > >> > According to the above suggestions, I conducted the following test:
> > > >> >
> > > >> > werner@X10DAi:~$ sudo useradd test
> > > >> > werner@X10DAi:~$ sudo passwd test # Set the pw as: asdf1234
> > > >> > werner@X10DAi:~$ sudo usermod -d /home/test -s /bin/bash test
> > > >> > werner@X10DAi:~$ sudo mkdir /home/test
> > > >> >
> > > >> > # This time, the problem discussed here doesn't appear again:
> > > >> > werner@X10DAi:~$ su - test
> > > >> > Password:
> > > >> > test@X10DAi:~$
> > > >> >
> > > >> > So, I tried to login back as follows and the problem appeared once more:
> > > >> >
> > > >> > test@X10DAi:~$ su - werner
> > > >> > Password:
> > > >> > terminate called after throwing an instance of 'std::runtime_error'
> > > >> > what(): Failed to create dbus connection
> > > >> > xhost: unable to open display ""
> > > >> > dirname: invalid option -- 'b'
> > > >> > Try 'dirname --help' for more information.
> > > >> > readlink: invalid option -- 'b'
> > > >> > Try 'readlink --help' for more information.
> > > >> >su - werner
> > > >> > Any tips for further debugging?
> > > >> if su - test works and su - werner failed
> > > >> then some script executed by werner login is failing.
> > > >>
> > > >> No idea why
> > > >>
> > > >> Message about dirname and readlink aught to be fixed.
> > > >>
> > > >> Apparently you are running some script executing those instructions that
> > > >> test does not execute.
> > > >>
> > > >> By the way, after spending years as an maintenance programmer I found it beneficial
> > > >> to fix any errors I find even if I believe they have no bearing on the problem
> > > >> I am trying to fix.
> > > >>
> > > >> For your xhost problem I would need to see the xhost command. Looking through my
> > > >> host xx__local.sh script I have
> > > >> # grep xhost xx__local.sh
> > > >> /local/bin/set_xhost +"$(hostname --fqdn)"
> > > >> /local/bin/set_xhost +localhost >
> > > >> xhost +local:docker
> > > >>
> > > >> You may want to consider install/using shellcheck to check your scripts.
> > > >
> > > > I wonder whether there is a similar but targeting for generating detail debug messages of startup scripts (profile, .bashrc, etc...).
> > > For debugging a script I use
> > > script -c "bash -x script_to_debug_here" a.log
> > >
> > > As for login scripts which I need to see when something changed modified
> > > /etc/profile to check if $HOME/debug is executable and if so run it.
> > > Test is before/after each login script. Example snippet from /etc/profile
> > > follows"
> > >
> > >
> > > for i in /etc/profile.d/*.sh /etc/profile.d/sh.local ; do
> > > if [ -r "$i" ]; then
> > > if [ "${-#*i}" != "$-" ]; then
> > > if [ -x $HOME/debug ] ; then
> > > . $HOME/debug "starting $i "
> > > fi
> > > . "$i"
> > > if [ -x $HOME/debug ] ; then
> > > . $HOME/debug "finished $i "
> > > fi
> > > else
> > > if [ -x $HOME/debug ] ; then
> > > . $HOME/debug "starting $i "
> > > fi
> > > . "$i" >/dev/null
> > > if [ -x $HOME/debug ] ; then
> > > . $HOME/debug "finished $i "
> > > fi
> > > fi
> > > fi
> > > done
> > Nice idea. Thank you very much again. I will try to follow your prompts for further inspection and testing.
> >
> > Regards,
> > Zhao
> feeeeresrsdrdcv

On Wednesday, January 25, 2023 at 10:28:34 PM UTC-6, hongy...@gmail..com wrote:
> Hi here,
>
> For Linux desktop login, say, Gnome, with the bash as the default shell, is there a method to save all the detailed sourced files information and the errors during the logging process?
>
> I often encounter strange phenomena and problems in login, but I don't know where they come from. Any tips will be appreciated.
>
> Regards,
> Zhaorffrfrrfrfrfrfrfrfrffrfr

On Wednesday, April 5, 2023 at 2:15:20 AM UTC-5, Jalen Q wrote:
> On Wednesday, January 25, 2023 at 10:28:34 PM UTC-6, hongy...@gmail.com wrote:
> > Hi here,
> >
> > For Linux desktop login, say, Gnome, with the bash as the default shell, is there a method to save all the detailed sourced files information and the errors during the logging process?
> >
> > I often encounter strange phenomena and problems in login, but I don't know where they come from. Any tips will be appreciated.
> >
> > Regards,
> > Zhaorffrfrrfrfrfrfrfrfrffrfr

On Wednesday, January 25, 2023 at 10:28:34 PM UTC-6, hongy...@gmail..com wrote:
> Hi here,
>
> For Linux desktop login, say, Gnome, with the bash as the default shell, is there a method to save all the detailed sourced files information and the errors during the logging process?
>
> I often encounter strange phenomena and problems in login, but I don't know where they come from. Any tips will be appreciated.
>
> Regards,
> Zhao

On Wednesday, January 25, 2023 at 10:28:34 PM UTC-6, hongy...@gmail..com wrote:
> Hi here,
>
> For Linux desktop login, say, Gnome, with the bash as the default shell, is there a method to save all the detailed sourced files information and the errors during the logging process?
>
> I often encounter strange phenomena and problems in login, but I don't know where they come from. Any tips will be appreciated.
>
> Regards,
> Zhao
gttttfftftftfggyygytytyttggggttggttgtgtgt66666666676ttyyyuy

On Wednesday, January 25, 2023 at 10:28:34 PM UTC-6, hongy...@gmail..com wrote:
> Hi here,
>
> For Linux desktop login, say, Gnome, with the bash as the default shell, is there a method to save all the detailed sourced files information and the errors during the logging process?
>
> I often encounter strange phenomena and problems in login, but I don't know where they come from. Any tips will be appreciated.
>
> Regards,
> Zhao
fffdtdfdfrrrdrdtdtttffrfrf