On Monday, January 30, 2023 at 9:34:21 AM UTC+8, hongy...@gmail.com wrote:
> On Thursday, January 26, 2023 at 8:12:15 PM UTC+8, Kees Nuyt wrote:
> > On Wed, 25 Jan 2023 23:17:06 -0800 (PST), "hongy...@gmail.com"
> > <hongy...@gmail.com> wrote:
> >
> > [...]
> > >werner@X10DAi:~$ ls /etc/profile.d/000-rootshare.sh
> > >/etc/profile.d/000-rootshare.sh
> > >werner@X10DAi:~$ ls ~/.profile.d/
> > >000-networkd-resolved-netplan-dnsmasq.bash 300-fcitx5-rime.bash
> > >001-dnsmasq-dnsproxy.bash 300-firefox.bash
> > [...]
> >
> > Binay search will take just a few tries.
> > Move half of the scripts in ~/.profile.d/ somewhere where they
> > will not run.
> > Try again.
> > - No error: the problem was in the half you moved away
> > - Still error: the problem was in the half you did not move
> >
> > Proceed by activating half of the set of scripts that has the
> > problem.
> > Repeat until the size of the set is one script.
> I've tried out the above method, and find that the "Are you sure you want to proceed?" problem is not caused by any scripts located under ~/.profile.d/. So what should I do for further examination?

Finally, it turns out that the problem is caused by a bug of a Ubuntu patch and the incorrect settings in my initialization scripts. See the following links for more details:

https://git.launchpad.net/ubuntu/+source/gdm3/tree/debian/patches/ubuntu/config_error_dialog.patch
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2005135
https://discourse.gnome.org/t/are-you-sure-you-want-to-proceed-message-on-login/13758/7

> > --
> > Kees Nuyt
> Zhao

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.

Any tips for further debugging?

Regards,
Zhao

On Sun, 5 Feb 2023 03:41:22 -0800 (PST), "hongy...@gmail.com"
<hongyi.zhao@gmail.com> wrote:

> Finally, it turns out that the problem is caused by a bug
> of a Ubuntu patch and the incorrect settings in my
> initialization scripts.

I'm glad you could solve it.
--
Kees Nuyt

On Monday, February 6, 2023 at 10:15:00 PM UTC+8, Kees Nuyt wrote:
> On Sun, 5 Feb 2023 03:41:22 -0800 (PST), "hongy...@gmail.com"
> <hongy...@gmail.com> wrote:
>
> > Finally, it turns out that the problem is caused by a bug
> > of a Ubuntu patch and the incorrect settings in my
> > initialization scripts.
> I'm glad you could solve it.

But Gunnar Hjalmarsson <2005135@bugs.launchpad.net> gives the alternative maybe nicer solution *:

--- begin quote ---
Gunnar Hjalmarsson (gunnarhj) wrote on 2020-07-12: #2

Second thoughts...

The --no-markup option prevents zenity from interpreting \n which makes the dialog hard to read in most cases. So only adding --no-markup is not a viable solution.

As a possible alternative I played with sed() a bit. The script includes this line:

TEXT="$PARA1\n\n$(fold -s $ERR)\n\n$PARA2"

My thought is to add a new line right after that. Something along these lines:

TEXT=$(printf '%s' "$TEXT" | sed 's/</\&lt;/g')

which would replace all occurrences of '<' with '&lt;'. Can you please test that and see if it helps in your case.
Changed in gdm3 (Ubuntu):
status: In Progress → Incomplete
Changed in lightdm (Ubuntu):
status: In Progress → Incomplete
summary: - lightdm config-error-dialog.sh should pass --no-markup
+ config-error-dialog.sh should pass --no-markup
--- end quote ---

Below is my comment on the above method:

--- begin quote ---
Thank you for letting me know your alternative nice solution. But
there are so many HTML Character Entities [1-2]. How does your method
deal with all these possible situations?

[1] https://www.w3schools.com/HTML/html_entities.asp
[2] https://stackoverflow.com/questions/5068951/what-do-lt-and-gt-stand-for
--- end quote ---

Any more comments, suggestions, and alternative enhancements for fixing this bug gracefully and thoroughly will be greatly appreciated.

* https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1887252
> --
> Kees Nuyt

Regards,
Zhao

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.

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.

Agreed. Nice idea!
> 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

Mine is as follows:

werner@X10DAi:~/Public/repo/github.com/bash-it/custom$ ug xhost
300-run-graphical-application-as-root-in-Wayland-session.bash: if ! xhost | grep -qE '^(LOCAL:|SI:localuser:root)'; then
300-run-graphical-application-as-root-in-Wayland-session.bash: # xhost local:
300-run-graphical-application-as-root-in-Wayland-session.bash: xhost si:localuser:root > /dev/null 2>&1
> You may want to consider install/using shellcheck to check your scripts.

Thank you for your advice.

Regards,
Zhao

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...).

Regards,
Zhao